Bug 1804700

Summary: openshift-apiserver should directly use the host-etcd IPs
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: openshift-apiserverAssignee: Luis Sanchez <sanchezl>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, mfojtik, sttts
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1805254 (view as bug list) Environment:
Last Closed: 2020-02-24 13:31:45 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: 1805254, 1805534    
Bug Blocks:    

Description David Eads 2020-02-19 13:25:36 UTC 
The host-etcd endpoint IPs do not change very often. This makes them more stable than relying on the "real" service endpoints, which reduces rollouts.

Using the IPs directly reduces the the dependency stack for working openshift-apiserver and should improve availability during upgrades.
Comment 2 David Eads 2020-02-24 13:31:03 UTC 
Until we work out a restart mechanism if all IPs for master nodes have changed, the kube-apiserver using the dns name is safer for the kube-apiserver.  the openshift-apiserver doesn't have a bootstrapping problem, so it can use IPs.
Comment 3 David Eads 2020-02-24 13:31:45 UTC 

*** This bug has been marked as a duplicate of bug 1805254 ***