From 149142e63ea149f2dbc5a9f2cd9c6e1713d38f8d Mon Sep 17 00:00:00 2001 From: fabriziopandini Date: Mon, 30 Jan 2023 10:49:53 +0100 Subject: [PATCH] nit on KCP proposal --- docs/proposals/20191017-kubeadm-based-control-plane.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/proposals/20191017-kubeadm-based-control-plane.md b/docs/proposals/20191017-kubeadm-based-control-plane.md index 487911a5e603..3bc2f35f13e1 100644 --- a/docs/proposals/20191017-kubeadm-based-control-plane.md +++ b/docs/proposals/20191017-kubeadm-based-control-plane.md @@ -479,7 +479,8 @@ When `MaxSurge` is set to 0 the rollout algorithm is as follows: replacement for the previous machine is not yet created. - The cluster MUST have no machines with a deletion timestamp. This rule prevents KCP taking actions while the cluster is in a transitional state. - Remediation MUST preserve etcd quorum. This rule ensures that we will not remove a member that would result in etcd - losing a majority of members and thus become unable to field new requests (note: this rule applies only to CP with at least replicas) + losing a majority of members and thus become unable to field new requests (note: this rule applies only to CP already + initialized and with managed etcd) - Additionally following opt-in safeguards will be put in place: - If we are remediating the same machine (delete, re-create, replacement machine gets unhealthy), it will be possible