Skip to content

Installer updates for the August 2026 6.0.3 release - #4542

Merged
tjmoore4 merged 1 commit into
CrunchyData:mainfrom
ValClarkson:installer_update_6.0.3
Aug 18, 2026
Merged

Installer updates for the August 2026 6.0.3 release#4542
tjmoore4 merged 1 commit into
CrunchyData:mainfrom
ValClarkson:installer_update_6.0.3

Conversation

@ValClarkson

Copy link
Copy Markdown
Contributor

Regenerated from operator-installers with
release-artifacts/prerelease/developer/release-manifest-ubi9.yaml and copied into config/ via make publish-public-installers.

Image tags moved from calver 2621 -> 2633 with the following version bumps (mirrors versioning.yaml):

  • postgres-operator 6.0: 6.0.2-0 -> 6.0.3-0
  • postgres-operator 5.8: 5.8.8-0 -> 5.8.9-0
  • crunchy-pgadmin4: ubi9-9.15 -> ubi9-9.17
  • crunchy-pgbackrest: ubi9-2.58.0 -> ubi9-2.59.0
  • crunchy-postgres-exporter: ubi9-0.18.1 -> ubi9-0.19.1
  • crunchy-postgres 15/16/17/18: 15.18/16.14/17.10/18.4 ->
    15.19/16.15/17.11/18.6 (and matching -gis variants)
  • crunchy-pgbouncer: ubi9-1.25 (unchanged upstream, calver-only bump)

app.kubernetes.io/version bumped 6.0.2 -> 6.0.3 in config/default/kustomization.yaml, config/singlenamespace/kustomization.yaml, and the three CRD label sets (pgadmins, pgupgrades, postgresclusters).

config/rbac/cluster/kustomization.yaml resource list reordered alphabetically by the installer generator (role.yaml before role_binding.yaml); functionally equivalent.

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • New feature
  • Bug fix
  • Documentation
  • Testing enhancement
  • Other

What is the current behavior (link to any open issues here)?

What is the new behavior (if this is a feature change)?

  • Breaking change (fix or feature that would cause existing functionality to change)

Other Information:

Regenerated from operator-installers with
release-artifacts/prerelease/developer/release-manifest-ubi9.yaml
and copied into config/ via `make publish-public-installers`.

Image tags moved from calver 2621 -> 2633 with the following version
bumps (mirrors versioning.yaml):

* postgres-operator 6.0: 6.0.2-0 -> 6.0.3-0
* postgres-operator 5.8: 5.8.8-0 -> 5.8.9-0
* crunchy-pgadmin4: ubi9-9.15 -> ubi9-9.17
* crunchy-pgbackrest: ubi9-2.58.0 -> ubi9-2.59.0
* crunchy-postgres-exporter: ubi9-0.18.1 -> ubi9-0.19.1
* crunchy-postgres 15/16/17/18: 15.18/16.14/17.10/18.4 ->
  15.19/16.15/17.11/18.6 (and matching -gis variants)
* crunchy-pgbouncer: ubi9-1.25 (unchanged upstream, calver-only bump)

app.kubernetes.io/version bumped 6.0.2 -> 6.0.3 in
config/default/kustomization.yaml, config/singlenamespace/kustomization.yaml,
and the three CRD label sets (pgadmins, pgupgrades, postgresclusters).

config/rbac/cluster/kustomization.yaml resource list reordered
alphabetically by the installer generator (role.yaml before
role_binding.yaml); functionally equivalent.
@ValClarkson
ValClarkson force-pushed the installer_update_6.0.3 branch from b73e651 to 62d9240 Compare August 17, 2026 21:20
@tjmoore4
tjmoore4 merged commit 4ed0c1c into CrunchyData:main Aug 18, 2026
24 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants