Repository navigation
chore: bump Percona Operator for PostgreSQL to 3.1.0 - #90
Merged
Merged
Conversation
- 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>
oksana-grishchenko
approved these changes
Nov 19, 2026
# 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps the Percona Operator for PostgreSQL from 3.0.0 to 3.1.0, the latest release (2026-09-09).
pg-operatordependency3.0.0→3.1.0. The subchart values are compatible (3.1.0 only adds an optionalworkers).github.com/percona/percona-postgresql-operator/v3, so imports switch from thev2pseudo-version tov3 v3.1.0(only indirect deps move otherwise; Kubernetes/controller-runtime unchanged). The provider setscrVersionfrompgversion.Version(), so instances move tocrVersion: 3.1.0once the operator is upgraded.e2e-tests/release_versions) and makes them the defaults:14.24-1,15.19-1,16.15-1,17.11.1-1,18.6.1-1(new default bundle)1.25.2-6, pgBackRest2.59.0-11.25.2-6(as before, all bundles use the pgBouncer certified with the operator). Instances on an existing bundle get a pgBouncer image roll.PG_OPERATOR_VERSION3.1.0 for CRD install and tests; upgrade tests start fromPREVIOUS_PG_OPERATOR_VERSION3.0.0.Compatibility checks
PerconaPGCluster/PerconaPGBackup/PerconaPGRestoreCRDs 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 thecrVersionformat, none of which the provider sets differently.extensions.builtindeprecated (not used by the provider).Testing
go test -race ./...andmake lintpass.Not included / follow-ups
pg_cronandset_useras built-in extensions (extensions.<name>.enabled), pluspg_tde, persistent logs and pgBouncer mTLS — candidates for provider parameters in follow-up PRs.3.1.xrow when the next provider version is cut.