To Reproduce Steps to reproduce the behavior:

1. Create a control plane with the following configuration.

   apiVersion: core.openstack.org/v1beta1
   kind: OpenStackControlPlane
   metadata:
     name: openstack-control-plane
     namespace: openstack
   spec:
     secret: osp-secret
     storageClass: lvms-vg1
     extraMounts:
       - name: horizon-tmp
         extraVol:
           - propagation:
             - Horizon
             extraVolType: Nfs
             mounts:
             - mountPath: /var/tmp
               name: horizon-tmp
             volumes: 
             - name: horizon-tmp
               nfs:
                 path: /var/nfs/horizon
                 server: 172.18.0.254
   

2. Deploy OpenStackControlPlane
3. Confirm horizon-tmp volume is not listed as volumes in deployment CR.

Expected behavior

• The top level extraMounts needs to be propagate to assigned component.

Bug impact

• The customer needs to create extraMounts for component level.

Known workaround

• Put the extraMounts under component level.

    horizon:
      apiOverride: {}
      enabled: true
      template:
        extraMounts:
          - name: horizon-tmp
            extraVol:
              - propagation:
                - Horizon
                extraVolType: Nfs
                mounts:
                - mountPath: /var/tmp
                  name: horizon-tmp
                volumes:
                - name: horizon-tmp
                  nfs:
                    path: /var/nfs/horizon
                    server: 172.18.0.254
        customServiceConfig: ""
        memcachedInstance: memcached
        override: {}
        preserveJobs: false
        replicas: 2
        resources: {}
        secret: osp-secret
        tls: {}