📖 Amend KCP proposal with remediation while provisioning the CP #7855
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
the
size/S
|
Thx! /lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 0e6c9a507def215537b3239e3e82a3c70d727137
|
|
@g-gaston: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
fabriziopandini
force-pushed
the
improve-kcp-remediation
branch
from
8f52b5f
to
ce3e77f
Compare
k8s-ci-robot
removed
the
lgtm
|
Addressed last nit, squashed commits |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 3441596600cbabcacaa16d6255da4e8ddbe2ec0b
|
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
| - 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. | ||
| losing a majority of members and thus become unable to field new requests (note: this rule applies only to CP with at least replicas) |
There was a problem hiding this comment.
| 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 with at least 3 replicas) |
?
There was a problem hiding this comment.
Thanks for following up, opened #8018
What this PR does / why we need it:
This PR proposes an amendment to KCP remediation so it will be possible to remediate failure happening while provisioning the CP (both first CP and CP machines while current replica < desired replica);
It also introduces opt-in control of remediation retry behavior.
Which issue(s) this PR fixes:
Rif #7496