OIDC Secret via Kubernetes

[ricardomolendijk]

We are trying to deploy Semaphore via the Helm chart and configure OIDC authentication. However, it seems that the chart currently does not support using Kubernetes Secrets or SealedSecrets for OIDC credentials.

This is a problem because:

• We cannot commit sensitive OIDC client ID/secret values to values.yaml.
• We want to follow best practices for secret management in Kubernetes.

It would be great if the Helm chart could support:

• Referencing Kubernetes Secrets for OIDC configuration fields.
• Avoiding the need to store sensitive credentials in plaintext in values.yaml.

This feature would allow secure and production-ready deployments with OIDC.

Thanks!