DCN Workaround to set Cinder uniquePodNames false

As per the OSPRH-11240, set uniquePodNames false for Cinder so that extraMounts can be used to propagate secrets to pods by matching the instance AZ name in DCN deployments. This patch can be reverted after OSPRH-11240 is resolved. Jira: https://issues.redhat.com/browse/OSPRH-11240 Signed-off-by: John Fulton <[email protected]>
openstack-k8s-operators · Nov 6, 2024 · c23b9ea · c23b9ea
1 parent 518a882
commit c23b9ea
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/dt/dcn/edpm-post-ceph/nodeset/kustomization.yaml b/dt/dcn/edpm-post-ceph/nodeset/kustomization.yaml
@@ -78,6 +78,17 @@ replacements:
           - spec.cinder.template.cinderBackup.customServiceConfig
         options:
           create: true
+  - source:
+      kind: ConfigMap
+      name: service-values
+      fieldPath: data.cinder.uniquePodNames
+    targets:
+      - select:
+          kind: OpenStackControlPlane
+        fieldPaths:
+          - spec.cinder.uniquePodNames
+        options:
+          create: true
   - source:
       kind: ConfigMap
       name: service-values

diff --git a/examples/dt/dcn/service-values.yaml b/examples/dt/dcn/service-values.yaml
@@ -8,6 +8,8 @@ metadata:
     config.kubernetes.io/local-config: "true"
 data:
   preserveJobs: false
+  cinder:
+    uniquePodNames: false
   cinderAPI:
     replicas: 3
     customServiceConfig: |