Closed razo7 closed 6 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: razo7
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test 4.14-openshift-e2e /test 4.15-openshift-e2e
/test 4.14-openshift-e2e /test 4.15-openshift-e2e
/test 4.14-openshift-e2e /test 4.15-openshift-e2e
/lgtm giving others a chance to review as well, feel free to unhold /hold
/retest
/test 4.14-openshift-e2e /test 4.15-openshift-e2e
/retest
/retest
/test 4.14-openshift-e2e
Moving from blocking CR creation on unhealthy nodes to better checking of unhealthy nodes, and CP guard pods prior to CR creation and any etcd quorum violation https://github.com/medik8s/common/pull/17
/retest
/retest
/test 4.13-openshift-e2e
/lgtm
/unhold
/retest
Fix etcd quorum check from looking only at DisruptionsAllowed to also looking for control plane node etcd guard pod. If there are no allowed disruptions and nm CR is for a node that is not disrupted, then we must not allow this CR creation as it would violate etcd quorum. Otherwise, when there is a failed guard pod (Ready status is False) or there is no guard pod for the node, then we allow the CR creation as it won't violate further the etcd quorum.
Furthermore, this etcd quorum check is only valid on OCP / OKD, since they have etcd quorum PDB. Thus, we won't run this validation on other platforms.
Originally the PR intended to block CR creation for any node, including workers that we currently support. It was decided to allow it for any node as long as the (control plane) node won't violate etcd quorum.
ECOPROJECT-1811