WIP bootkube.sh populate complete list of etcd endpoints during bootstrap#2998
WIP bootkube.sh populate complete list of etcd endpoints during bootstrap#2998hexfusion wants to merge 2 commits intoopenshift:masterfrom
Conversation
|
/test e2e-gcp |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test e2e-azure |
limit flake /test e2e-aws |
03041cd to
7525812
Compare
|
/test e2e-gcp |
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
7525812 to
4ba7073
Compare
|
/test e2e-gcp |
|
/test e2e-aws-upgrade |
|
/test e2e-gcp One last try but it appears we will need openshift/cluster-etcd-operator#60 |
886e674 to
da1ac09
Compare
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
da1ac09 to
21aa688
Compare
|
/test e2e-gcp |
|
/test e2e-azure |
|
After testing we have decided to continue with openshift/cluster-etcd-operator#58 and will continue that work on the installer via #3005 |
|
@hexfusion: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
This PR attempts to reduce initial bootstrap complexity caused by only populating the bootstrap endpoint. By feeding apiserver the entire list during bootstrap we avoid the scenario where
cluster-etcd-operatorcompletes scaling up to 4 members. The result of this scaling is the host-etcd service is also adjusted to reflect all of the scaled etcd endpoints. Meanwhile, the cluster-kube-apiserver-operator has not yet rolled out the new static pod assets in the correct revision. So when we reap the bootstrap node we leave apiserver with a single backend endpoint pointing at the bootstrap node that is no longer alive.In the previous version of the etcd client balancer, this would have proven overly disruptive but the new balancer handles the sub connection round-robin failover very gracefully.
We consider this a short term solution while we improve the timings and complexity around this process.
Requires openshift/cluster-etcd-operator#60