Closed tplavcic closed 4 months ago
@tplavcic could you please check upgrade-minor test
Test name | Status |
---|---|
custom-extensions | passed |
demand-backup | passed |
init-deploy | passed |
monitoring | passed |
operator-self-healing | passed |
scaling | passed |
scheduled-backup | passed |
self-healing | passed |
start-from-backup | passed |
telemetry-transfer | passed |
upgrade-minor | failure |
users | passed |
We run 12 out of 12 |
commit: https://github.com/percona/percona-postgresql-operator/pull/703/commits/a7c720f8775e22651095c4bb8388e3523d40cff6
image: perconalab/percona-postgresql-operator:PR-703-a7c720f87
CHANGE DESCRIPTION
Problem: Manual steps need to be taken to prepare release branch and also to prepare main branch after release branch is merged.
Solution: With this manifests will be prepared but also next version and main images set in cr.yaml. What we need to still do manually is set specific database/backup and other images before the release since each product has it's own.
Prepare release example:
make release VERSION=2.5.0 IMAGE_TAG_BASE=percona/percona-postgresql-operator
Prepare main branch after release example:
make after-release VERSION=main IMAGE_TAG_BASE=perconalab/percona-postgresql-operator
this above will automatically generate next version.also works:
make after-release NEXT_VER=2.6.0 IMAGE=perconalab/percona-postgresql-operator:main
CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
Config/Logging/Testability