Skip to content

Commit 9596d86

Browse files
committed
Incorporated Gennady's comments
1 parent 28b978a commit 9596d86

File tree

2 files changed

+15
-43
lines changed

2 files changed

+15
-43
lines changed

modules/configuring/con-mounting-and-container-targeting-details.adoc

Lines changed: 5 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -3,51 +3,18 @@
33
[id="con-mounting-and-container-targeting-details_context"]
44
= Mounting and Container Targeting Details
55

6-
The mounting behavior is determined by the combination of the optional `key` and `mountPath` fields. Use the `containers` field (available since `v1alpha4`/`v0.8`) to specify targets other than the default container.
6+
The mounting behavior is determined by the combination of the optional `key` and `mountPath` fields. Use the `containers` field (available since `v1alpha4`/`v1.8`) to specify targets other than the default container.
77

88
.Container targeting options
99
|===
1010
| Configuration | Target Containers
1111

1212
| No or empty `containers` field
13-
| Only the **`backstage-backend`** container (default).
13+
| Only the `backstage-backend` container (default).
1414

1515
| `containers: ["*"]`
16-
| **All** containers in the Pod.
16+
| All containers in the Pod.
1717

1818
| Explicit container names
19-
| Only the containers listed (e.g., `backstage-backend`, `install-dynamic-plugins`).
20-
|===
21-
22-
.File mounting behavior
23-
24-
[cols="1,1,1", options="header"]
25-
|===
26-
| Configuration | Mounting Behavior | Watch/Update Status
27-
28-
| Nothing specified
29-
| Each key/value mounts as filename/content with `subPath`.
30-
| Resources are watched by the Operator and the Pod is refreshed on change.
31-
32-
| `key` specified (with or without `mountPath`)
33-
| The specified key/value mounts with `subPath`.
34-
| Resources are watched by the Operator.
35-
36-
| Only `mountPath` specified
37-
| A directory containing all key/values mounts without `subPath`.
38-
| Related resources are typically auto-updated by Kubernetes.
39-
|===
40-
41-
[NOTE]
42-
====
43-
For security reasons, mounting files from **Secrets** is not supported if both `mountPath` and `key` are unspecified.
44-
====
45-
46-
.PersistentVolumeClaim (PVC) path logic
47-
48-
PVCs mount as a directory. The mount path is determined by the first available value in the following order:
49-
50-
. `spec.application.extraFiles.pvcs[].mountPath` (Specific path for the PVC).
51-
. `spec.application.extraFiles.mountPath` (Default path for all extra files).
52-
. The {backstage} container `WorkingDir`.
53-
. The default Kubernetes path: `/opt/app-root/src`.
19+
| Only the containers listed (for example, `backstage-backend`, `install-dynamic-plugins`).
20+
|===

modules/configuring/proc-injecting-custom-files-and-environment-variables-into-backstage-containers.adoc

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,9 @@
44
[id="proc-injecting-custom-files-and-environment-variables-into-backstage-containers"]
55
= Injecting extra files and environment variables into {backstage} containers
66

7-
You must use the `spec.application` path to configure the injection of extra files and environment variables into your {backstage} Pod containers. This ensures necessary configurations, credentials, and dependencies (such as certificates) are available at runtime.
8-
97
By default, files mount only to the `backstage-backend` container. If the `containers` field is not specified, the volume mounts to the `backstage-backend` container only. You can also specify other targets, including a list of containers by name (such as `dynamic-plugin-install` or custom sidecars) or opt to in all containers in the {backstage} Pod.
108

11-
. To mount files, PVCs, and injecting environment variables into different container targets., apply the configuration to your `{product-custom-resource-type} custom resource (CR)` as shown in the following code:
9+
. To mount files and injecting environment variables into different container targets, apply the configuration to your `{product-custom-resource-type} custom resource (CR)` as shown in the following code:
1210
+
1311
[source,yaml]
1412
----
@@ -80,6 +78,14 @@ The files are mounted with the following paths and container targets:
8078
| `/my/cm3/path/` (Directory)
8179
| `backstage-backend`, `install-dynamic-plugins`
8280

81+
| Secrets (`secret1`)
82+
| `/my/path/file3.txt`
83+
| `install-dynamic-plugins`
84+
85+
| Secrets (`secret2`)
86+
| `/my/secret2/path`
87+
| `backstage-backend`
88+
8389
| PVC (`myclaim1`)
8490
| `/my/path/myclaim1` (Directory)
8591
| `backstage-backend` only
@@ -94,5 +100,4 @@ The files are mounted with the following paths and container targets:
94100

95101
| Env Var (`MY_VAR`)
96102
| `MY_VAR = my-value`
97-
| `install-dynamic-plugins` only
98-
|===
103+
| `install-dynamic-plugins` only

0 commit comments

Comments
 (0)