Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document the usage of CustomConfigMaps and Secrets while deploying through Helm #19

Open
gopaddle-io opened this issue Aug 10, 2021 · 2 comments
Open

Document the usage of CustomConfigMaps and Secrets while deploying through Helm #19

gopaddle-io opened this issue Aug 10, 2021 · 2 comments

Comments

@gopaddle-io
Copy link
Owner

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
@gopaddle-io
Copy link
Owner Author

  1. Separate directory for CRDs - crds folder is used to place the CRD definitions in the chart
  2. Only helm install supported. --dry-run and upgrade options are not supported for CDRs
  3. 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.

@juliohm1978
Copy link
Contributor

I believe this has been addressed by #41.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@juliohm1978 @gopaddle-io