postgres-operator/pkg/cluster
Oleksii Kliukin f9e14d2517 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.
2017-11-30 12:36:06 +01:00
..
cluster.go Rename api roles configuration parameter. 2017-11-22 10:43:35 +01:00
exec.go return idle status when worker has nothing to do 2017-10-11 15:42:20 +02:00
filesystems.go Make use of kubernetes client-go v4 2017-07-25 15:25:17 +02:00
k8sres.go Tweak our reaction to the cluster upgrade process. 2017-11-30 12:36:06 +01:00
pg.go Fix the connection leak and user options sync. 2017-11-27 16:46:34 +01:00
pod.go Tweak our reaction to the cluster upgrade process. 2017-11-30 12:36:06 +01:00
resources.go use sync methods while updating the cluster 2017-11-03 12:00:43 +01:00
sync.go Allow global configuration options for API roles. 2017-11-22 10:43:35 +01:00
types.go add comments on roles 2017-09-11 17:44:32 +02:00
util.go use sync methods while updating the cluster 2017-11-03 12:00:43 +01:00
volumes.go use sync methods while updating the cluster 2017-11-03 12:00:43 +01:00