Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1797122

Summary: kubeapiserver rollout with storage config takes more time on update during bootstrap
Product: OpenShift Container Platform Reporter: Alay Patel <alpatel>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4   
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: Environment:
Last Closed: 2020-05-13 21:58:32 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:

Description Alay Patel 2020-01-31 23:43:46 UTC 
Description of problem:

kube-apiserver rolls out new pod every time storage config changes. storage config depends on host-etcd. To avoid this start host-etcd will all four etcd (bootstrap and all 3 masters). This will make sure that the very first rollout of kubeapiserver is configured with more urls and reduce bootstrap time because of cluster-etcd-operator. 

The clustermembercontroller needs more chatter, add other resource informers
Comment 2 ge liu 2020-03-09 07:51:42 UTC 
No regression issue found.
Comment 4 errata-xmlrpc 2020-05-13 21:58:32 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:0581