weave-gitops
weave-gitops copied to clipboard
HelmCharts with GitOps Run
As a user, I want to pull down someone's latest pull request and run gitops run against the helm charts on that branch.
- I expect my values to be copied over from an existing helm release if one exists.
- I should be able to run
gitops runagainst the same resource without conflicts. - As a user, I expect
gitops runto clean up any resources I've created when I turn it off, even if those resources are no longer referenced by the manifests.
As a user, I want to pull down someone's latest pull request and run gitops run against a kustomization overlay on that branch.
- I already have a kustomization overlay running on a cluster and I expect to be able to run against that same overlay with gitops run.
- I should be able to run
gitops runagainst the same resource without conflicts. - I don't want gitops run to be smart about whether the cluster is bootstrapped or not. I just want to run
gitops runknowing I have done all of that.
Acceptance Criteria
Helm
- As a user, I want to be able to leverage the existing values that are set on a helm release if one is already running.
- As a user, I expect to be able to leverage the existing secrets that are be used by the existing workload.
- As a user, when I run against a helm chart and there is no helm release then I expect
gitops runto create a helm release object on my behalf. - As a user, if I wanted to customize the helm release values I can and those would take precedence over the original helm release values.
- When I run against a helm chart I would expect a temporary
HelmReleaseto be created and not aKustomization.
@chanwit and @ozamosi this is part of the phase 2 initiative. I could probably use your eyes on it before planning.
Ref: https://fluxcd.io/flux/guides/helmreleases/#define-a-helm-release
Let's do #2886 first, as it's smaller.
@fsequeira1: "seems like a lot of work"