Bug 1804717

Summary: improve reliability during upgrade by using a deployment
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: openshift-apiserverAssignee: Maru Newby <mnewby>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, dahernan, jinjli, lstanton, mfojtik, mnewby, openshift-bugs-escalate, sttts, wking
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:
: 1805388 1805872 (view as bug list) Environment:
Last Closed: 2020-07-13 17:16:11 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:    
Bug Blocks: 1805872    

Description David Eads 2020-02-19 14:02:06 UTC 
DaemonSets are special cased during host shutdown and don't get a chance to gracefully fail over.  This can cause problems with both connectivity on a kill (non-grace shutdown) and sudden loss of etcd connection.

Switching to a deployment will alleviate symptoms.  We original chose a daemonset for spreading and for scaling.  For spreading, we now have anti-affinity rules.  For scaling, we should wire into something like an HPA anyway.

The migration will require PRs back to 4.3 which remove the deployment on downgrade and in 4.4 to remove the daemonset.
Comment 1 Maru Newby 2020-02-27 07:16:05 UTC 
Resetting status to allow follow-on PR to use the same bz.
Comment 5 Ryan Phillips 2020-05-11 15:05:40 UTC 
*** Bug 1790989 has been marked as a duplicate of this bug. ***
Comment 8 Ryan Phillips 2020-05-14 18:41:49 UTC 
*** Bug 1790989 has been marked as a duplicate of this bug. ***
Comment 10 errata-xmlrpc 2020-07-13 17:16:11 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