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.

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

Research: Automation of Helm Chart releases and maintenance #426

Closed
Tracked by #394
mowies opened this issue Nov 16, 2022 · 0 comments
Closed
Tracked by #394

Research: Automation of Helm Chart releases and maintenance #426

mowies opened this issue Nov 16, 2022 · 0 comments
Assignees
Milestone

Comments

@mowies
Copy link
Member

mowies commented Nov 16, 2022

This ticket shall be used to track research for #394.

Generally, the plan is to have a separate place for the helm chart and then have separate releases and version numbers that get released automatically through the chart-releaser-action.

Important questions and unknowns that shall be researched:

  • can we fully generate a helm chart through kustomize?
  • should we combine kustomize with helm or can we maybe replace kustomize with helm?
    • if we combine kustomize with helm, how would that affect the future maintainablilty of the project?
  • how would the process look like when a user requests a feature for the helm chart, e.g. a new helm value?
  • should we maintain 2 types of how to install the KLT? (manifests/helm)
  • if we decide to use helm, should we keep the charts in the same project, or create a separate project for the helm charts and maintain them there?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants