During a cluster upgrade there's currently no guarantee any control plan component
will keep at least one of its pods available. To ensure there is at least one pod available when the master nodes are getting drained, a PDB for each core component is created.
For more information please see https://issues.redhat.com/browse/WRKLDS-293.
KS, KCM and KA need additional logic alongside the PDBs. Their resolution is tracked through https://bugzilla.redhat.com/show_bug.cgi?id=2005901.
Could find pdb for multi-nodes cluster :
[root@localhost ~]# oc project openshift-kube-controller-manager
Now using project "openshift-kube-controller-manager" on server "https://api.yinzhou-30.qe.devcluster.openshift.com:6443".
[root@localhost ~]# oc get pdb
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
kube-controller-manager-guard-pdb 2 N/A 1 110m
can't find pdb for SNo:
[root@localhost roottest]# oc get node
NAME STATUS ROLES AGE VERSION
ip-10-0-153-252.us-east-2.compute.internal Ready master,worker 35m v1.23.3+b63be7f
[root@localhost roottest]# oc project openshift-kube-controller-manager
Now using project "openshift-kube-controller-manager" on server "https://api.yinzhou-bugr.qe.devcluster.openshift.com:6443".
[root@localhost roottest]# oc get pdb
No resources found in openshift-kube-controller-manager namespace.
[root@localhost roottest]# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-arm64-2022-01-29-162645 True False 16m Cluster version is 4.10.0-0.nightly-arm64-2022-01-29-162645
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.