Description of problem:
kube-apiserver pod performs connectivity checks to report on network outages. Sometimes when debugging certain types of issues, the activity from the connectivity checks results in too much data, making it more difficult to pinpoint the root cause. We need to be able to temporarily disable the connectivity checks.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.0-0.nightly-2020-10-09-224055 True False 5h59m Cluster version is 4.6.0-0.nightly-2020-10-09-224055
Updated the KubeAPIServer as following,
$ oc edit kubeapiserver cluster
After that, the kube-apiserver ran into CrashLoopBackOff,
$ oc get pods -n openshift-kube-apiserver --show-labels | grep kube-apiserver
kube-apiserver-kewang1061-tnbbj-master-0.c.openshift-qe.internal 4/5 CrashLoopBackOff 8 5h59m apiserver=true,app=openshift-kube-apiserver,revision=6
kube-apiserver-kewang1061-tnbbj-master-1.c.openshift-qe.internal 4/5 CrashLoopBackOff 8 6h3m apiserver=true,app=openshift-kube-apiserver,revision=6
kube-apiserver-kewang1061-tnbbj-master-2.c.openshift-qe.internal 4/5 Running 8 6h2m apiserver=true,app=openshift-kube-apiserver,revision=6
The fix doesn't work, so assign back.
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.7.0 security, bug fix, and enhancement 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.