Skip to content

Publish helm chart to repo for tools like ArgoCD (et al.) #4539

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

Closed
jskrzypek opened this issue Oct 13, 2022 · 2 comments
Closed

Publish helm chart to repo for tools like ArgoCD (et al.) #4539

jskrzypek opened this issue Oct 13, 2022 · 2 comments
Assignees

Comments

@jskrzypek
Copy link

ArgoCD is a pretty popular tool for managing K8s deployments. ArgoCD will let you specify a helm repository & chart and take the work & uncertainty out of managing deployed apps.

To use coder's helm chart as you are currently providing it (i.e. the coder_helm_<VERSION>.tgz artifact on the release), I would need to manually download and commit that file to my gitops repo to get it deployed. This largely defeats the purpose of ArgoCD.

If, however, the newer coder (AFAICT you are calling it Coder OSS/Coder Enterprise V2?) chart gets published to a publicly available helm repository, then it's something I can point to from, e.g., ArgoCD's helm chart controller or even a kustomize chart-inflater.

Would this be possible?
For now I have a workaround... Since I'm mostly evaluating Coder for now anyhow I just went ahead and published my own helm-charts repo for this purpose (https://jskrzypek.github.io/helm-charts/index.yaml) I did this by just manually downloading the chart from your releases and running helm repo index . on the folder. I guess that's technically more steps, but hopefully you guys will publish it yourselves at some point...

@bpmct
Copy link
Member

bpmct commented Oct 13, 2022

We definitely plan on hosting our Helm repository! Glad to hear you have a workaround but we'll get to this soon :)

@bpmct
Copy link
Member

bpmct commented Oct 18, 2022

Closing as duplicate of #3545

@bpmct bpmct closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants