Done
Details
Assignee
inel.pandzicinel.pandzicReporter
Diogo RecharteDiogo RecharteNeeds QA
YesFix versions
Affects versions
Priority
Medium
Details
Details
Assignee
inel.pandzic
inel.pandzicReporter
Diogo Recharte
Diogo RecharteNeeds QA
Yes
Fix versions
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created March 16, 2023 at 10:55 AM
Updated March 5, 2024 at 3:51 PM
Resolved April 12, 2023 at 9:45 AM
In PXC/PSMDB operators there's the `pause` field that allows the user to pause/restart the cluster.
In the PG operator v2.0.0 there are two fields in the CR spec `paused` and `shutdown`. Looking at the documentation I was expecting that `shutdown` had a similar behavior to the `pause` field in PXC/PSMDB however, when I set it to `true`, I saw no change to the cluster state. Even though the documentation mentions a different purpose, I also tried with `paused` just because but had the same result (no change).
Steps to reproduce
kubectl apply --server-side -f https://raw.githubusercontent.com/percona/percona-postgresql-operator/v2.0.0/deploy/bundle.yaml
kubectl apply -f https://raw.githubusercontent.com/percona/percona-postgresql-operator/v2.0.0/deploy/cr.yaml
Add `shutdown: true` to the CR spec
Notice that no change was reflected to the cluster state/pods