Skip to content

chore: bump Percona Operator for PostgreSQL to 3.1.0 - #90

Merged
oksana-grishchenko merged 4 commits into
mainfrom
chore/bump-pg-operator-3.1.0
Nov 19, 2026
Merged

oksana-grishchenko merged 4 commits into
mainfrom
chore/bump-pg-operator-3.1.0

Conversation

@spron-in

@spron-in spron-in commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

What

Bumps the Percona Operator for PostgreSQL from 3.0.0 to 3.1.0, the latest release (2026-09-09).

  • Helm: pg-operator dependency 3.0.0 → 3.1.0. The subchart values are compatible (3.1.0 only adds an optional workers).
  • Go module: 3.1.0 moved the module to github.com/percona/percona-postgresql-operator/v3, so imports switch from the v2 pseudo-version to v3 v3.1.0 (only indirect deps move otherwise; Kubernetes/controller-runtime unchanged). The provider sets crVersion from pgversion.Version(), so instances move to crVersion: 3.1.0 once the operator is upgraded.
  • Version catalog: adds the images certified with 3.1.0 (from the operator's e2e-tests/release_versions) and makes them the defaults:
    • PostgreSQL 14.24-1, 15.19-1, 16.15-1, 17.11.1-1, 18.6.1-1 (new default bundle)
    • pgBouncer 1.25.2-6, pgBackRest 2.59.0-1
    • Existing bundles stay, and every bundle now uses pgBouncer 1.25.2-6 (as before, all bundles use the pgBouncer certified with the operator). Instances on an existing bundle get a pgBouncer image roll.
  • CI/tests: PG_OPERATOR_VERSION 3.1.0 for CRD install and tests; upgrade tests start from PREVIOUS_PG_OPERATOR_VERSION 3.0.0.

Compatibility checks

  • PerconaPGCluster/PerconaPGBackup/PerconaPGRestore CRDs 3.0.0 → 3.1.0: no removed fields, no newly required fields. New CEL rules only cover new features (pg_tde, logicalReplicas, tls.certManagementPolicy) and the crVersion format, none of which the provider sets differently.
  • Release notes: PMM2 support removed (the provider already uses PMM 3); extensions.builtin deprecated (not used by the provider).
  • New images verified to exist on Docker Hub.

Testing

  • go test -race ./... and make lint pass.

Not included / follow-ups

  • 3.1.0 adds pg_cron and set_user as built-in extensions (extensions.<name>.enabled), plus pg_tde, persistent logs and pgBouncer mTLS — candidates for provider parameters in follow-up PRs.
  • The README compatibility table is per release; it needs a 3.1.x row when the next provider version is cut.

- pg-operator Helm dependency 3.0.0 -> 3.1.0
- Go module: the operator moved to github.com/percona/percona-postgresql-operator/v3
  in 3.1.0, so imports switch from the v2 pseudo-version to v3 v3.1.0. The
  provider sets crVersion from it, so instances are moved to crVersion 3.1.0.
- Version catalog: add the images certified with 3.1.0 (PostgreSQL 14.24-1,
  15.19-1, 16.15-1, 17.11.1-1, 18.6.1-1, pgBouncer 1.25.2-6, pgBackRest
  2.59.0-1) and make them the defaults; every bundle uses pgBouncer 1.25.2-6.
- PG_OPERATOR_VERSION 3.1.0 for CRDs and tests; upgrade tests start from 3.0.0.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Sergey Pronin <sp@solanica.io>
Brings in pgHBA (#89), the PMM contract module (#88) and #93. The new
pg_hba code imported the operator's v2 module path; switch it to v3 to
match the 3.1.0 bump.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
# Conflicts:
#	charts/provider-percona-postgresql/generated/provider-spec.yaml
#	go.mod
#	go.sum
#	internal/provider/backup_mirror.go
#	internal/provider/backup_mirror_test.go
#	internal/provider/provider.go
Signed-off-by: Oksana Grishchenko <oksana.grishchenko@percona.com>
@oksana-grishchenko
oksana-grishchenko merged commit 59edce2 into main Nov 19, 2026
12 checks passed
@oksana-grishchenko
oksana-grishchenko deleted the chore/bump-pg-operator-3.1.0 branch November 19, 2026 12:59
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