-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0
-
No
-
Rejected
-
False
-
In case of SNO we should only have 1 replica for the hypershift operator pod.
Currently I'm seeing
oc --kubeconfig ~/kubeconfig get pod -n hypershift NAME READY STATUS RESTARTS AGE operator-54585fd87b-nd6pq 0/1 Pending 0 4d18h operator-54585fd87b-p8lxg 1/1 Running 0 4d23h
The pending pod shows the following warning:
Warning FailedScheduling 27m (x3181 over 4d18h) default-scheduler 0/1 nodes are available: 1 node(s) didn't match pod anti-affinity rules. preemption: 0/1 nodes are available: 1 node(s) didn't match pod an ti-affinity rules..
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.0 security update