configurator
configurator copied to clipboard
Document the usage of CustomConfigMaps and Secrets while deploying through Helm
Is your feature request related to a problem? Please describe. None
Describe the solution you'd like With Helm 3, it is easier to deploy CRDs. We need to investigate and suggest best practices around deploying CustomConfigMaps and Secrets via Helm Charts.
Describe alternatives you've considered None
Additional context None
- Separate directory for CRDs - crds folder is used to place the CRD definitions in the chart
- Only helm install supported. --dry-run and upgrade options are not supported for CDRs
- We can provide a separate helm chart for installing CRDs. CustomConfigMaps and CustomSecrets can be used directly in the helm templates once the CRDs are installed.
I believe this has been addressed by https://github.com/gopaddle-io/configurator/pull/41.