Bug 1705646

Summary:	MUST VERIFY All components must use configmap leader lock file, not endpoints
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Master	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:48:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Clayton Coleman 2019-05-02 16:27:35 UTC

This bug was initially created as a copy of Bug #1705645

I am copying this bug because: this team must ensure they are not impacted:

Scheduler was using leader-elect-resource-lock endpoints, must be configmap.

I0502 15:23:30.593107       1 flags.go:33] FLAG: --kubeconfig=""
I0502 15:23:30.593111       1 flags.go:33] FLAG: --leader-elect="true"
I0502 15:23:30.593114       1 flags.go:33] FLAG: --leader-elect-lease-duration="15s"
I0502 15:23:30.593118       1 flags.go:33] FLAG: --leader-elect-renew-deadline="10s"
I0502 15:23:30.593122       1 flags.go:33] FLAG: --leader-elect-resource-lock="endpoints"
I0502 15:23:30.593126       1 flags.go:33] FLAG: --leader-elect-retry-period="2s"
I0502 15:23:30.593130       1 flags.go:33] FLAG: --lock-object-name="kube-scheduler"

Components *must not* use leader-elect-resource-lock=endpoints because it causes high churn on kube-proxies.  This is also not a safe change to roll out, so is a 4.1 blocker.

Comment 1 Michal Fojtik 2019-05-02 17:27:21 UTC

https://github.com/openshift/cluster-kube-controller-manager-operator/blob/master/bindata/v3.11.0/kube-controller-manager/defaultconfig.yaml#L22

Comment 3 errata-xmlrpc 2019-06-04 10:48:19 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, 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/RHBA-2019:0758