-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19
-
None
This is a clone of issue OCPBUGS-45943. The following is the description of the original issue:
—
Description of problem:
1 Client can not connect to the kube-apiserver via kubernetes svc, as the kubernetes svc is not in the cert SANs 2 The kube-apiserver-operator generate apiserver certs, and insert the kubernetes svc ip from the network cr status.ServiceNetwork 3 When the temporary control plane is down, and the network cr is not ready yet, Client will not connect to apiserver again
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. I have just met this for very rare conditions, especially when the machine performance is poor 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-45943 Empty status.ServiceNetwork field causes x509: cannot validate certificate for xxx.xxx.xx.xx which doesn't contain any IP SANs
- Verified
- is blocked by
-
OCPBUGS-45943 Empty status.ServiceNetwork field causes x509: cannot validate certificate for xxx.xxx.xx.xx which doesn't contain any IP SANs
- Verified
- links to