Bug 1804700 - openshift-apiserver should directly use the host-etcd IPs
Summary: openshift-apiserver should directly use the host-etcd IPs
Keywords:
Status: CLOSED DUPLICATE of bug 1805254
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.4.0
Assignee: Luis Sanchez
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1805254 1805534
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-19 13:25 UTC by David Eads
Modified: 2020-02-24 13:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1805254 (view as bug list)
Environment:
Last Closed: 2020-02-24 13:31:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.