-
Notifications
You must be signed in to change notification settings - Fork 62
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
publish helm charts #17
Comments
Aside from the CRDs, the manifests are minimal, and there's an expectation that you'll need or want to customize them for a production environment. I'll continue to revisit this as I work towards 1.0. As for Helm charts, I've been chatting with others in the community of the best way to have those packaged up. |
Thank you for the quick response! I will just copy the files and wait for the helm chart to be published. |
Moving my original comment to this thread
|
@terinjokes Any updates on this? |
@terinjokes this has been a long time since this has been addressed - This doesn't cause a lot of confidence in the project, even if you commit the index.yaml we could use this helm chart remotely. eg: However, without even the index.yaml being commit we're stuck with cloning and rendering these manifests which is a large PITA. |
@xunholy I don't use Helm, so I'm not entirely sure what is missing. This is also an open source project of one person (me), getting this done is part of being happy with a 1.0 release. |
@terinjokes In order to use Helm, a In the ideal world, this file is hosted somewhere behind something like a website. As part of GitHub Actions/Helm workflows everything is automatic, it only requires a In the minimal world, @xunholy's suggestion makes the trick (i.e. manually creating and maintaining an |
I was hoping the Chart.yaml would be enough for folks to get started. Of course the tools would require more unnecessary complexity. I'll reluctantly go set this up. |
While I understand your reply, the unnecessary complexity here is honestly quite necessary to actually use the chart with Helm correctly and definitely not that complex. |
No no, I'm not saying you're making it complex, or even that the index.xml is complex. I'm just thinking they made the common use case (use a chart from a GitHub release) involve more steps than necessary. |
Ah ok 🙂 True. I think this is the main cost of decentralizing services, Helm being not relative to any "official" package provider/server. |
@terinjokes is there anything further we can do to help this progress? I do see the PR that will hopefully address this already but if there is anything else please reach out 🙏 |
We've experimentally published charts at |
Can we expect this release any time soon, and is this documentation currently available anywhere? |
tested the helm chart and it works. Will update readme |
I am trying to set up Origin CA Issuer automatically using Terraform. The problem I have is that you need to clone the repository to install it.
It would be very simple to do if the yaml files in each step were combined into a single file. That way you can apply it using the raw github url, like with the CRDs:
kubectl apply -f https://raw.githubusercontent.com/cloudflare/origin-ca-issuer/trunk/deploy/crds/cert-manager.k8s.cloudflare.com_originissuers.yaml
It would also be nice if something like https://github.com/helm/chart-releaser-action was used to publish the helm chart.
The text was updated successfully, but these errors were encountered: