ibm-messaging / mq-helm

Apache License 2.0
28 stars 34 forks source link

Multiple mqsc Config Maps not working #9

Closed pfaulkn closed 2 years ago

pfaulkn commented 2 years ago

When using multiple CMs in the Helm chart only the last CM is used to map to a volume

mqscConfigMaps:

Results in

image

callumpjackson commented 2 years ago

I've attempted to re-produce the above using the following helm values:

license: accept
queueManager:
  mqscConfigMaps:
    - name: config1
      items:
        - config1item1.mqsc
        - config1item2.mqsc
    - name: config2
      items:
        - config2item1.mqsc
        - config2item2.mqsc

This generates the expected stateful set configuration shown below:

      volumes:
      - name: mqsc-cm-config1
        configMap:
          name: config1
          defaultMode: 420
          items:
            - key: config1item1.mqsc
              path: config1item1.mqsc
            - key: config1item2.mqsc
              path: config1item2.mqsc
      - name: mqsc-cm-config2
        configMap:
          name: config2
          defaultMode: 420
          items:
            - key: config2item1.mqsc
              path: config2item1.mqsc
            - key: config2item2.mqsc
              path: config2item2.mqsc

I'm guessing the issue is slightly more complex in nature and may depend on the entire helm properties that you are using. Could you provide all of these so we can try and re-produce?

callumpjackson commented 2 years ago

Resolved as a spacing issue in the original yaml, once this was corrected everything is working as expected.