Keycloak Operator KeyCloakClient CR secret and Helm: how to avoid commits with secrets?

[Hector Salazar]

Hello,

What's the recommended way to specify a client secret without checking it in source control?

I noticed that the KeyCloak operator takes the value and creates a secret, but I want to avoid commits with secret values in my source control.

Is there a pattern for secrets in Helm that is compatible with the KeyCloakClient CR?

Thanks,

Hector

[Robert Schuh]

The operator creates the secret automatically if you dont define one in the CR and your helm chart should then reference the secret, there is no need to check in any secret values, the helm chart would only need to know the deterministically generate secret name in kubernetes