Skip to content

feat: add publish of helm chart to ghcr.io #2853

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.

Sign up for GitHub

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

Open
a1994sc wants to merge 6 commits into
base: master
Choose a base branch
from
+12 −0
Open

feat: add publish of helm chart to ghcr.io #2853

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
90f1cc9
feat: add publish of helm chart to ghcr.io
a1994sc Jan 25, 2025
7cdf692
Merge branch 'master' into master
a1994sc Feb 18, 2025
c9ed36f
Merge branch 'master' into master
a1994sc Feb 27, 2025
0562716
Merge branch 'master' into master
a1994sc Mar 26, 2025
6faa7fb
Merge branch 'master' into master
a1994sc Jun 13, 2025
1fac45b
Merge branch 'master' into master
FxKu Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/publish_ghcr_image.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,3 +86,15 @@ jobs:
build-args: BASE_IMAGE=ubuntu:22.04
tags: "${{ steps.image_lb.outputs.BACKUP_IMAGE }}"
platforms: linux/amd64,linux/arm64

- name: Build and push postgres-operator chart to ghcr
run: |
helm package charts/postgres-operator
helm push postgres-operator-*.tgz oci://${{ env.REGISTRY }}/zalando/charts
rm -rf postgres-operator-*.tgz

- name: Build and push postgres-operator-ui chart to ghcr
run: |
helm package charts/postgres-operator-ui
helm push postgres-operator-ui-*.tgz oci://${{ env.REGISTRY }}/zalando/charts
rm -rf postgres-operator-ui-*.tgz
Copy link
Copy Markdown
Member

@FxKu FxKu Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this work out of the box? I would assume helm needs to be installed first fr this GH workflow step to work.

Copy link
Copy Markdown
Author

@a1994sc a1994sc Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Helm is installed by default on the github runners:

https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md

Copy link
Copy Markdown
Author

@a1994sc a1994sc Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@FxKu

Copy link
Copy Markdown
Member

@FxKu FxKu Apr 27, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@a1994sc Sorry, helm is usually not a priority for us. Don't you need a login step like helm registry login ... or is this already covered with the existing login step?

Copy link
Copy Markdown
Author

@a1994sc a1994sc Apr 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Helm will use the docker config setup by the docker/login-action action you use to publish the docker images

Copy link
Copy Markdown
Member

@FxKu FxKu Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do keep past releases of the helm chart in the chart directories. When you run helm package it would include all releases in the zipped file, right? Should it maybe only contain the last release?

Copy link
Copy Markdown
Author

@a1994sc a1994sc May 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I call helm package which creates the tar ball in the root of the repo, then pushes that to the ghcr registry. As a result, there should be no major concern with leaving those past releases in place