-
Notifications
You must be signed in to change notification settings - Fork 195
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 chart as OCI artifact to ghcr.io #1683
publish Helm chart as OCI artifact to ghcr.io #1683
Conversation
Does this require up front work regarding granting permissions? I have no familiarity with configuring anything related to ghcr, packages, and I don't see anything in settings that leads to such. |
When I tested this in my own gh account the "package" had default visibility of private after I published it and needed to be modified by the owner to be publicly downloadable in the GitHub UI |
637b458
to
a50c42b
Compare
dffc7cb
to
b8fa761
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hopefully this workflow will result in some publications.
I've requested org-level permissions to make packages public, hopefully this will be granted tomorrow. |
in lieu of publishing a tgz as a GitHub release artifact, this change publishes (on tag
helm/${semver}
) the Helm chart bundled as an OCI artifact to the GitHub container registry, i.e. ghcr.io. I also updated the installation instructions which are now less gory. This change requires granting public read access to the corresponding buildfarm "package" within the bazel-buildfarm project. It defaults to private.