Skip to content

fix(k8s): repin CNPG to 18.4.0-sr4 after Harbor GC'd the 18.3.0-sr5 digest #3

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

Merged
mfreeman451 merged 1 commit into from
Oct 3, 2026
Merged

fix(k8s): repin CNPG to 18.4.0-sr4 after Harbor GC'd the 18.3.0-sr5 digest #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 6 additions & 4 deletions k8s/base/pg-cluster.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,12 @@ metadata:
spec:
instances: 2

# Pin by digest: the floating 18.3.0-sr2-a78b3afd tag was GC'd from Harbor and
# left replicas in ImagePullBackOff (blocking Argo health). Use the same
# digest as control-plane / demo.
imageName: registry.carverauto.dev/serviceradar/serviceradar-cnpg:18.3.0-sr5@sha256:c349a1d34aef056f818630e0766501b5c98fa7598bdeee38d59d677a94cb18c9
# Pin by digest. The previous 18.3.0-sr5@sha256:c349a1d3... digest was
# garbage-collected from Harbor, leaving replicas in ImagePullBackOff
# (serviceradar-control#34). 18.4.0-sr4 is the digest the control-plane and
# demo clusters run; this DB only uses plpgsql, so the PG 18.3 -> 18.4 minor
# bump needs no extension changes.
imageName: registry.carverauto.dev/serviceradar/serviceradar-cnpg:18.4.0-sr4@sha256:59e442dec59fac3149e3a3c49ba0cc2987bfb052bca1a0ea8c01b4bb31427d1d

postgresql:
parameters:
Expand Down
Loading