Bug 1805449

Summary:	Ensure kube-apiserver advertises the correct IP on bare metal clusters
Product:	OpenShift Container Platform	Reporter:	Russell Bryant <rbryant>
Component:	kube-apiserver	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED ERRATA	QA Contact:	Ke Wang <kewang>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified	CC:	aos-bugs, mfojtik, sttts, xxia
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1805445	Environment:
Last Closed:	2020-07-13 17:16:52 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:
Bug Depends On:
Bug Blocks:	1805445, 1805865

Description Russell Bryant 2020-02-20 19:52:38 UTC

+++ This bug was initially created as a clone of Bug #1805445 +++

On a bare metal cluster, kube-apiserver's default behavior for choosing which IP to advertise may choose the wrong IP on a bare metal cluster that has some Virtual IPs.  See this PR for more details: https://github.com/openshift/cluster-kube-apiserver-operator/pull/760

Comment 3 errata-xmlrpc 2020-07-13 17:16:52 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-2020:2409