Split configuration between many ConfigMap / Secret

[gbonnefille]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

Configuring all aspects of Dex via a single config: key in a single values.yaml is not so easy.
Having the ability to pass piece of configuration via ConfigMap / Secret would offer more flexibility.

For example, I wish to publish a Dex with a preconfigured connectors but I want to delay or dynamically load configurations related to staticClients or staticPasswords.

1. I deploy Dex
2. I depoy the clients with their own configurations part for Dex

Proposed Solution

Perhaps with a Helm key like:

staticClientsSecrets:
- myFirstClient
- mySecondClient

These Secrets are mounted in /etc/dex/clients.d and an initContainer is responsible of assembling the config: part and these parts.

PS : it is probably simpler if these feature of splitting configuration is directly supported by Dex.

Alternatives Considered

No response

Additional Information

No response