operator
operator copied to clipboard
tektoncd
Is the Tekton Helm chart published?
Is the Tekton helm chart published in a chart repository? currently, the instructions point to cloning the git repository and installing the helm chart from there which isn't entirely useful for automated installs, especially if a dependent chart to another helm chart.
@jacksgt any update when we would be able to publish the chart? cc @vdemeester
@tlawrie sorry for the delay. @jacksgt has contributed the helm chart to the project, just waiting for him to give a go. then we can work on publishing the chart :)
@tlawrie I am looking into helm, it is a bit new for me 😅 will try to get this done soon :)
Do you have any questions? I've done a helm chart in the past.
Is it in figuring out where to package and host it?
Do you have any questions? I've done a helm chart in the past.
Is it in figuring out where to package and host it?
Yeah Currently, I am updating the chart in main branch for the latest released version of operator and once it works fine was thinking to setup github action for the release https://github.com/marketplace/actions/helm-chart-releaser WDYT?
Hey folks, thanks for the interest and sorry for the long delay!
I created a PR a while ago that should automatically update the Helm chart for each new version of the operator: https://github.com/tektoncd/operator/pull/816 Unfortunately, so far no one has tested that PR :-/
Once we have that in place, using the helm-chart-releaser action as suggested above should be fairly straightforward.
I created a PR a while ago that should automatically update the Helm chart for each new version of the operator: #816 Unfortunately, so far no one has tested that PR :-/
hey @jacksgt sorry for that. The PR has a work in progress label due to which I didn't take a look earlier. Let me take a look.
hey @tlawrie #816 might take time to get merged. automation will take some time to setup as I don't access to the release cluster.
so till then we will update the chart manually and https://github.com/tektoncd/operator/pull/1006 is for creating a release. we will be releasing 0.61.0 today or on monday. once that is done, I will update the chart for it.
please feel free to contribute any improvements to chart or chart release workflow. 🙃
Any update on this? Additionally, 0.62.0 from September is not implemented in the chart.
I'm more than happy to help with the Helm Chart. I've done a few over the last couple of months for a couple of OSS projects that had less than ideal installation guides. I'd normally offer to do the standard manifests that users use to install Tekton but as the operator is the recommended way of installing and managing Tekton I'm more than happy to contribute to this as I really like Tekton and I do think that the only thing holding it back from widespread adoption is the complexity of it.
If I can help reduce that complexity of installation into usable Helm Charts, I'd be more than happy to do this. Additionally, I'd like to also implement TektonChains into the chart also? As for me this is the powerful aspect of Tekton that separates it from other CI tools. Let me knows your thoughts.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Hey folks,
this is currently blocked on https://github.com/tektoncd/operator/issues/1330
We already have a Helm chart: https://github.com/tektoncd/operator/tree/main/chart
and also automated CI for publishing the chart: https://github.com/tektoncd/operator/blob/main/.github/workflows/helm-release.yaml
As mentioned in the issue above, there is currently a minor permission issue with the CI and the repository needs to enable GitHub Pages - then we're good to go!
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
Can someone with permissions please re-activate issue #1330 and mark it fresh... it seems a shame to bury all that work when the only thing blocking publication of the helm charts is permissions and an overzealous bot.
Raised #1915 which augments this effort by allowing the repository to be used directly via the helm-git plugin.