Skip to content
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 Jenkins Helm charts to an OCI registry #1180

Closed
jonesbusy opened this issue Aug 27, 2024 · 7 comments · Fixed by #1197
Closed

Publish Jenkins Helm charts to an OCI registry #1180

jonesbusy opened this issue Aug 27, 2024 · 7 comments · Fixed by #1197
Labels
enhancement New feature or request

Comments

@jonesbusy
Copy link
Contributor

Is your feature request related to a problem? Please describe

This is to track about publishing the chart into OCI registry instead of the "legacy" format

The index is now stored on https://charts.jenkins.io/index.yaml which is the legacy helm YAML format. Recent Helm version (since 3.8) seems to move to the standard OCI format

What are your though about that ?

Probably something that could be discussed with Jenkins infra team as well

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

@jonesbusy jonesbusy added the enhancement New feature or request label Aug 27, 2024
@timja
Copy link
Member

timja commented Aug 27, 2024

What benefit does this give?


DockerHub would probably be my preference, but GitHub container registry might be the easiest.

@jonesbusy
Copy link
Contributor Author

What benefit does this give?

Use standard registry, no scalling issue with the index.yaml, eventually attach attestation etc...

DockerHub would probably be my preference, but GitHub container registry might be the easiest.

Probably will change the way the chart is released (similar to the Jenkins container image ? trusted ci ?)

@timja
Copy link
Member

timja commented Aug 28, 2024

For GitHub no secrets would be required. For docker hub we can probably add a GitHub secret

@jonesbusy
Copy link
Contributor Author

jonesbusy commented Sep 12, 2024

Resources

helm/chart-releaser-action#107
helm/helm#11062
https://github.com/fluxcd-community/helm-charts/pull/94/files

Nothing to do atannotation level. The package would be directly referenced to the correct repo because of the first URL in the source

sources:
  - https://github.com/jenkinsci/jenkins

I did also some test with my fork and helm publish work well

helm package charts/jenkins
helm registry login ghcr.io -u <username>

annotations
provenance

There are other repositories that publish their charts on both traditional and OCI storage: https://github.com/fluxcd-community/helm-charts/pkgs/container/charts%2Fflux2

It would allow consumer their prefered way of consuming the artifact

@felipecrs
Copy link
Contributor

felipecrs commented Sep 12, 2024

I think you just forgot to make the package public:

$ helm install jenkins oci://ghcr.io/jenkinsci/helm-charts/jenkins
Error: INSTALLATION FAILED: GET "https://ghcr.io/v2/jenkinsci/helm-charts/jenkins/tags/list": unexpected status code 403: denied: permission_denied: read_package

There should be a setting to make it public at https://ghcr.io/jenkinsci/helm-charts/jenkins.

@timja
Copy link
Member

timja commented Sep 12, 2024

Updated, @jonesbusy did you want to also update the README with the installation instructions here? https://github.com/jenkinsci/helm-charts/pkgs/container/helm-charts%2Fjenkins#usage

@jonesbusy
Copy link
Contributor Author

Sure I will open a PR tomorrow with OCI details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants