You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, when using a helm chart subscription, kargo has the following two ways to promote a new chart that is pushed to a helm chart repository:
Non-gitops: update a live argocd app spec with the new semvers
GitOps: update a subchart in an umbrella chart at a git path
These have the following drawbacks:
Option 1 is not really gitops, and specific to Argo CD
While Option 2 is gitops, it forces the use of an umbrella chart, which has the drawback of dependent values being nested under a field in the top values.yaml.
Kargo should provide a third option, which would download and untar the full helm chart to a chosen location in git.
Motivation
One use case is to avoid the use of the umbrella chart, which seems unnecessary when there is a single chart needs to be promoted.
Proposed Feature
Today, when using a helm chart subscription, kargo has the following two ways to promote a new chart that is pushed to a helm chart repository:
These have the following drawbacks:
Kargo should provide a third option, which would download and untar the full helm chart to a chosen location in git.
Motivation
One use case is to avoid the use of the umbrella chart, which seems unnecessary when there is a single chart needs to be promoted.
Users of Kustomize's chart inflator would benefit from fully inflated charts in git.
Suggested Implementation
As an alternative to updating the semvers of a file in git, extract the helm tarball to a specified location.
The text was updated successfully, but these errors were encountered: