- name: CATALOG_ENTITIES_EXTRACT_DIR
    value: '/extensions'
volumeMounts:

Reference reasoning: Similar deployment/config YAML in the repo sets filesystem path env vars as plain scalars (e.g., /opt/app-root/src/.npmrc.dynamic-plugins), indicating a consistent convention that avoids introducing unnecessary quoting differences.

1. redhat-developer/rhdh-chart/charts/backstage/values.yaml [160-178]
2. redhat-developer/rhdh-operator/pkg/model/testdata/janus-deployment.yaml [36-58]
3. redhat-developer/rhdh-operator/pkg/model/testdata/janus-deployment.yaml [94-96]
4. redhat-developer/rhdh-operator/examples/pvc-dp-cache.yaml [60-83]
5. redhat-developer/rhdh-operator/examples/pvc-dp-cache.yaml [84-94]
6. redhat-developer/rhdh-operator/integration_tests/testdata/rhdh-replace-dynaplugin-root.yaml [1-14]
7. redhat-developer/rhdh-chart/charts/backstage/ci/with-custom-dynamic-pvc-claim-spec-values.yaml [2-27]
8. redhat-developer/rhdh-chart/charts/backstage/values.yaml [37-44]

Instead of mounting the same volume to both /extensions and /marketplace for
backward compatibility, consider using a symbolic link. This simplifies the
Kubernetes manifests and avoids a confusing dual-mount pattern.

Examples:

            - name: extensions-catalog
              mountPath: /extensions
            - name: extensions-catalog
              # TODO(asoro): legacy path for backward compatibility. Will be removed in a near future.
              mountPath: /marketplace
              readOnly: true

                - name: extensions-catalog
                  mountPath: /extensions
                - name: extensions-catalog
                  # TODO(asoro): legacy path for backward compatibility. Will be removed in a near future.
                  mountPath: /marketplace
                  readOnly: true

Solution Walkthrough:

Before:

# In deployment.yaml
spec:
  template:
    spec:
      containers:
      - name: backstage
        volumeMounts:
        - name: extensions-catalog
          mountPath: /extensions
        - name: extensions-catalog
          # TODO: legacy path for backward compatibility
          mountPath: /marketplace
          readOnly: true
        ...
      volumes:
      - name: extensions-catalog
        emptyDir: {}

After:

# In deployment.yaml
spec:
  template:
    spec:
      containers:
      - name: backstage
        command: ["/bin/sh", "-c"]
        args:
          - ln -s /extensions /marketplace && <original_command>
        volumeMounts:
        - name: extensions-catalog
          mountPath: /extensions
        ...
      volumes:
      - name: extensions-catalog
        emptyDir: {}

Improve security by making the extensions-catalog volume mount at /extensions
read-only for the main container.

config/profile/rhdh/default-config/deployment.yaml [158-159]

 - name: extensions-catalog
   mountPath: /extensions
+  readOnly: true

• Apply / Chat

 			mainContainerExpectedVolumeMounts := []corev1.VolumeMount{
 				{
+					Name:      "dynamic-plugins-root",
 					MountPath: "/opt/app-root/src/dynamic-plugins-root",
-					SubPath:   "",
-				},
-				{
+				},
+				{
+					Name:      model.AppConfigDefaultName(backstageName),
 					MountPath: "/opt/app-root/src/default.app-config.yaml",
 					SubPath:   "default.app-config.yaml",
 				},
 				{
+					Name:      "extensions-catalog",
 					MountPath: "/extensions",
 				},
 				{
+					Name:      "temp",
 					MountPath: "/tmp",
-					SubPath:   "",
 				},
 			}
 
@@ -144,7 +146,7 @@
 				for _, vm := range mainCont.VolumeMounts {
 					if evm.MountPath == vm.MountPath {
 						found = true
-						g.Expect(vm.MountPath).To(Equal(evm.MountPath))
+						g.Expect(vm.Name).To(Equal(evm.Name))
 						g.Expect(vm.SubPath).To(Equal(evm.SubPath))
 					}

Include the expected Name (and ReadOnly where applicable) for the new mounts and
assert against it, so the test ensures /extensions and /marketplace are backed
by extensions-catalog as intended.

integration_tests/rhdh-config_test.go [122-142]

 mainContainerExpectedVolumeMounts := []corev1.VolumeMount{
 	{
+		Name:      "dynamic-plugins-root",
 		MountPath: "/opt/app-root/src/dynamic-plugins-root",
 		SubPath:   "",
 	},
 	{
+		Name:      utils.GenerateVolumeNameFromCmOrSecret(model.AppConfigDefaultName(backstageName)),
 		MountPath: "/opt/app-root/src/default.app-config.yaml",
 		SubPath:   "default.app-config.yaml",
 	},
 	{
+		Name:      "extensions-catalog",
 		MountPath: "/extensions",
+		SubPath:   "",
 	},
 	{
+		Name:      "extensions-catalog",
 		MountPath: "/marketplace",
+		SubPath:   "",
 		ReadOnly:  true,
 	},
 	{
+		Name:      "temp",
 		MountPath: "/tmp",
 		SubPath:   "",
 	},
 }

[To ensure code accuracy, apply this suggestion manually]

Document the new extensions-catalog volume and the CATALOG_ENTITIES_EXTRACT_DIR
default (including the 1.9+ behavior and the /marketplace legacy mount and its
planned removal) so users understand where catalog entities are extracted and
how to override/disable it.

docs/configuration.md [1]

-...
+## Extension catalog entities (1.9+)
 
+Starting with **RHDH 1.9**, the Operator mounts an `emptyDir` volume named `extensions-catalog` and configures dynamic plugin catalog extraction into it.
+
+- Default extract directory: `CATALOG_ENTITIES_EXTRACT_DIR=/extensions`
+- Mounted paths:
+  - `/extensions` (read/write)
+  - `/marketplace` (read-only **legacy** path for backward compatibility; will be removed in a future release)
+
+If you customize the Deployment/Pod template, ensure the `extensions-catalog` volume and corresponding mounts are preserved, or set `CATALOG_ENTITIES_EXTRACT_DIR` to match your desired mount path.
+

[To ensure code accuracy, apply this suggestion manually]

Enhance the integration test by adding an explicit assertion to verify the
presence and configuration of the extensions-catalog volume.

integration_tests/rhdh-config_test.go [113]

 g.Expect(deploy.PodSpec().Volumes).To(HaveLen(8))
+{
+    found := false
+    for _, v := range deploy.PodSpec().Volumes {
+        if v.Name == "extensions-catalog" {
+            found = true
+            g.Expect(v.EmptyDir).NotTo(BeNil())
+        }
+    }
+    g.Expect(found).To(BeTrue())
+}

• Apply / Chat

- name: extensions-catalog
  mountPath: /extensions
- name: extensions-catalog
  # TODO(asoro): legacy path for backward compatibility. Will be removed in a near future.
  mountPath: /marketplace
  readOnly: true

Reference reasoning: Existing operator-managed deployment YAML consistently mounts each volume a single time per container (e.g., default-config and plugin-deps), avoiding multiple mount points to the same backing volume. Aligning with that pattern reduces ambiguity and makes access mode expectations clearer.

1. redhat-developer/rhdh-operator/pkg/model/testdata/janus-deployment.yaml [36-58]
2. redhat-developer/rhdh-operator/dist/rhdh/install.yaml [2994-3005]
3. redhat-developer/rhdh-operator/dist/backstage.io/install.yaml [2096-2100]
4. redhat-developer/rhdh-operator/config/manager/deployment.yaml [91-95]
5. redhat-developer/rhdh-operator/integration_tests/testdata/spec-deployment.yaml [1-23]
6. redhat-developer/rhdh-operator/pkg/model/testdata/janus-deployment.yaml [94-96]
7. redhat-developer/rhdh-operator/examples/pvc-dp-cache.yaml [60-83]
8. redhat-developer/rhdh-operator/integration_tests/testdata/rhdh-replace-dynaplugin-root.yaml [1-14]