-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19.0
-
None
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-46010. The following is the description of the original issue:
—
Description of problem:
Bootstrapping currently waits to observe 2 endpoints in the "kubernetes" service in HA topologies. The bootstrap kube-apiserver instance itself appears to be included in that number. Soon after observing 2 (bootstrap instance plus one permanent instance), the bootstrap instance is torn down and leaves the cluster with only 1 instance. Each rollout to that instance causes disruption to kube-apiserver availability until the second permanent instance is started for the first time, easily totaling multiple minutes of 0% kube-apiserver availability.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-46010 Bootstrap kube-apiserver removal leaves only one endpoint in kubernetes service
- ON_QA
- is blocked by
-
OCPBUGS-46010 Bootstrap kube-apiserver removal leaves only one endpoint in kubernetes service
- ON_QA
- links to