-
- Downloads
Tweak our reaction to the cluster upgrade process.
Previously, the operator started to move the pods off the nodes to be decomissioned by watching the eol_node_label value. Every new postgres pod has been created with the anti-affinity to that label, making sure that the pods being moved won't land on another to be decomissioned node. The changes introduce another label that indicates the ready node. The new pod affinity will esnure that the pod is only scheduled to the node marked as ready, discarding the previous anti-affinity. That way the nodes can transition from the pending-decomission to the other statuses (drained, terminating) without having pods suddently scaled to them. In addition, rename the label that triggers the start of the upgrade process to node_eol_label (for consistency with node_readiness_label) and set its default vvalue to lifecycle-status:pending-decomission.
Showing
- manifests/configmap.yaml 2 additions, 1 deletionmanifests/configmap.yaml
- pkg/cluster/k8sres.go 2 additions, 2 deletionspkg/cluster/k8sres.go
- pkg/cluster/pod.go 1 addition, 1 deletionpkg/cluster/pod.go
- pkg/controller/node.go 3 additions, 3 deletionspkg/controller/node.go
- pkg/util/config/config.go 2 additions, 1 deletionpkg/util/config/config.go
Please register or sign in to comment