-
Notifications
You must be signed in to change notification settings - Fork 110
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
Helm chart #278
Comments
@eddycharly thanks, I think it would be a nice idea. We do have an operator already, but there's a whole ecosystem of people that uses prominently helm, so it would be good. |
Sure, i will be happy to maintain it. I also have a couple of prow jobs to automate releasing new versions of the chart. On the hosting side, it can be as easy as putting a tar.gz and index.yaml in a bucket. That's the easiest solution, another option is to use chartmuseum. I currently use chartmuseum because it is hosted on a private chart repository but for public charts, there's nothing better/more cost efficient than the bucket solution i guess. |
I'll try to open a PR today or tomorrow, it will be easier to discuss about it. |
OK - thank you. Would you like to add the PR to the experimental repo? |
Ok for the experimental repo. |
I opened a PR with some WIP here tektoncd/experimental#494 I started with a copy of my helm chart and took the opportunity to rewrite/improve a few things. |
Thinking about a versioning policy for helm charts. A good approach would be to use the same major and minor version as the target Tekton component, keeping the patch to increment on bug fixes. In any case, the Ok for you ? |
Closing. Too broad. More relevant issues exist in the experimental repo. |
I'm using a helm chart i wrote to deploy Tekton for a few months now and it's working great.
Would you be interested in a contribution for this ?
The text was updated successfully, but these errors were encountered: