Repository navigation
Publish Helm Chart as an OCI artifact #78
Description
Hey!
I was wondering if there's any interest in publishing the helm chart as an OCI Artifact?
In theory it should be as simple as the below
- uses: azure/setup-helm@v5.0.1
- name: Login to GitHub Container Registry
uses: docker/login-action@v4
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- id: push
name: Push helm chart
working-directory: operator/build/helm/kubernetes
run: helm push postgresql-operator-${{ steps.nextVersion.outputs.version }}.tgz oci://ghcr.io//aboutbits/postgresql-operator/chart
Activity
ThoSap commentedon Oct 23, 2026
Hi, thanks for your interest.
We will definitely do that 👍🏻
userbradley commentedon Oct 23, 2026
Ah! You've done it already haha!!
I was going to see if there's interest then submit the PR but you've beaten me to it.
Thanks!
ThoSap commentedon Oct 23, 2026
Haha, no worries ;)
I will create a new release in ~1 hour.
ThoSap commentedon Oct 24, 2026
v0.8.0 is released, and the Helm chart is now published as an OCI artifact to GHCR:
To get notified of new versions, subscribe to the releases of this repository: Watch → Custom → Releases.
@Danielduel @fredordercloud @wesselOC @rudolfduplessis we recommend that you install v0.8.0. It fixes CVE-2026-54291 for PostgreSQL connections with
channelBinding=requirein theClusterConnectionparameters, and it updates many dependencies, among them Quarkus to 3.40.1.1 (LTS). See the release notes for the changes to check before an upgrade.P.S. @userbradley if this project works out for you well, please consider starring the repository.
ThoSap commentedon Oct 24, 2026
Small follow-up: from v0.8.1 on, the Helm chart is published to
oci://ghcr.io/aboutbits/helm-chartsinstead ofoci://ghcr.io/aboutbits/charts(#88). This is the same approach Grafana uses with grafana/helm-charts → https://grafana.github.io/helm-charts.v0.8.0 stays available at the old coordinate, but new versions are only published to the new one. Please update the chart reference when you upgrade.
ThoSap commentedon Oct 25, 2026
v0.8.2 is released, and we recommend that you update to it:
It fixes several bugs in the status handling. For example, a
Database,SchemaorRolecould keep an oldPENDINGorERRORphase after its cause went away, and aDatabaseorSchemawithoutownerwent toERRORon its second reconcile. The CRDs are the same as in 0.8.1, so no manual CRD update is necessary. See the upgrade notes for the behavior changes to check before the upgrade.