Bug 1876166

Summary:	need to be able to disable kube-apiserver connectivity checks
Product:	OpenShift Container Platform	Reporter:	Luis Sanchez <sanchezl>
Component:	kube-apiserver	Assignee:	Luis Sanchez <sanchezl>
Status:	CLOSED ERRATA	QA Contact:	Ke Wang <kewang>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs, mfojtik, sttts, xxia
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1876167 1887634 (view as bug list)		Environment:
Last Closed:	2021-02-24 15:17:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1887634, 1887718

Description Luis Sanchez 2020-09-06 00:22:52 UTC

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.

Comment 3 Ke Wang 2020-10-10 08:10:19 UTC

$ 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
spec:
  unsupportedConfigOverrides:
    operator:
      enableConnectivityCheckController: "True"

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.

Comment 10 errata-xmlrpc 2021-02-24 15:17:26 UTC

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.

https://access.redhat.com/errata/RHSA-2020:5633