[ISSUE] The comments explaining the use of existingSecret settings are incorrect

[daniel-ewing]

Describe the issue:

The comments explaining the use of existingSecret settings are incorrect for all settings like: global.identity.auth.[componentName].existingSecret. See, for example values.yaml#L128-L129, which states:

        # Identity.auth.connectors.existingSecret can be used to use an own existing secret. If not set a random secret is generated.
        # The existing secret should contain an `connectors-secret` field, which will be used as secret for the Identity-Connectors communication.

Actual behavior:

If used this way, global.identity.auth.[componentName].existingSecret contains the actual value of the secret stored in the [componentName]-secret field of an auto-generated secret with the name [deploymenyName]-[componentName]-secret.

Expected behavior:

The comment should accurately explain the behavior described above and the values.yaml should also explain that if you want to provide the name of an existing secret that contains a [componentName]-secret field, the correct syntax is global.identity.auth.[componentName].existingSecret.name

How to reproduce:

Try it.

Logs:

Not relevant.

Environment:

• Platform: minikube
• Chart version: 8.2.6

[proxyvert]

hi @daniel-ewing, I have the same issue https://github.com/camunda/camunda-platform-helm/issues/760

[floric]

See https://github.com/camunda/camunda-platform-helm/issues/760#issuecomment-1628790337 :) good luck