Random secret for connectors fails to be generated

[daniel-ewing]

Describe the issue:

When existingSecret values for global.identity components as well as identity.keycloak components are configured in the values.yaml, the random secret for connectors fails to be generated and an undocumented secret <deploymentName>-connectors-identity-secret with the key connectors-secret is required.

Actual behavior:

Identity and connectors do not start. From kubectl get pods:

NAME	READY	STATUS	RESTARTS	AGE
dev-connectors-5858b79b6f-87tqr	0/1	CreateContainerConfigError	0	129m
dev-identity-649dd5b465-rlf9g	0/1	CrashLoopBackOff	29 (19s ago)	129m

• If <deploymentName>-connectors-identity-secret with the key connectors-secret has been created, then connectors and identity will run correctly.
• I can find no indication that this configuration is required. The helm values.yaml L130-133 states: If not set a random secret is generated.

Expected behavior:

Everything starts.

How to reproduce:

1. Use a values.yaml that is configured with existingSecret values for global.identity components as well as identity.keycloak components.
2. NOTE: This configuration requires the creation of additional undocumented secrets named <deploymentName>-keycloak and <deploymentName>-postgresql-web-modeler to work - I created issue 644 for this.

Logs:

logs-identity.txt
decribe-connectors.txt

Environment:

Platform: Minikube on Ubuntu Linux
Helm CLI version: 3.10.1
Chart version: 8.2.0
Values file: values.yaml

[hisImminence]

8.2 version is not supported anymore. Will close as outdated.