K8SPG-543: fix panic - Githubissues

percona / percona-postgresql-operator

Percona Operator for PostgreSQL

https://www.percona.com/doc/kubernetes-operator-for-postgresql/index.html

Apache License 2.0

258 stars 50 forks source link

K8SPG-543: fix panic #708

Closed pooknull closed 3 months ago

pooknull commented 4 months ago

https://perconadev.atlassian.net/browse/K8SPG-543

DESCRIPTION

Problem: Applying a cr.yaml with empty .spec.proxy field caused operator to panic.

Solution: Set correct defaults.

CHECKLIST

Jira

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

Tests

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

Config/Logging/Testability

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

JNKPercona commented 3 months ago

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	passed
users	passed
We run 12 out of 12

commit: https://github.com/percona/percona-postgresql-operator/pull/708/commits/58719fddd98c62feb2ead3400f040b22fdf5f204 image: perconalab/percona-postgresql-operator:PR-708-58719fddd