K8SPG-561 update go to 1.22

[hors]

CHANGE DESCRIPTION

Problem: Short explanation of the problem.

Cause: Short explanation of the root cause of the issue if applicable.

Solution: Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

• [ ] Is the Jira ticket created and referenced properly?
• [ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• [ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• [ ] Is an E2E test/test case added for the new feature/change?
• [ ] Are unit tests added where appropriate?

Config/Logging/Testability

• [ ] Are all needed new/changed options added to default YAML files?
• [ ] Are the manifests (crd/bundle) regenerated if needed?
• [ ] Did we add proper logging messages for operator actions?
• [ ] Did we ensure compatibility with the previous version or cluster upgrade process?
• [ ] Does the change support oldest and newest supported PG version?
• [ ] Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
demand-backup	passed
upgrade	passed
version-service	passed
init-deploy	failed
scheduled-backup	passed
smart-update	passed
scaling	passed
recreate	passed
affinity	passed
monitoring	passed
self-healing	passed
operator-self-healing	passed
clone-cluster	passed
tls-check	passed
users	passed
ns-mode	passed
data-migration-gcs	passed
We run 17 out of 17

commit: https://github.com/percona/percona-postgresql-operator/pull/723/commits/7ed19e7088f23a7647f3a66d00778a83fac223e9 image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-pgo-apiserver

image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-pgo-event

image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-pgo-rmdata

image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-pgo-scheduler

image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-postgres-operator

image: perconalab/percona-postgresql-operator:PR-723-7ed19e708-pgo-deployer