One of the goals for Single Node OpenShift is to handle 60 seconds API downtime gracefully. This bug tracks the tweaks including the leader election lease duration needed in various components to achieve the goal.
I think we should decide if this is required to consider SNO as GA. If it's required for that and SNO is GA in 4.9 then we should mark all the dependent bugs as blocker+ rather than leaving it up to all of the teams to decide one by one whether or not they care enough.
Since this is a public bug, I have no idea which release SNO is considered GA nor am I making a prediction that it will be 4.9. I'm just saying we should assert a common approach to these bugs.
Moving to 4.10.0 as that's the .0 release under development.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.