Epic Goal

• The RolloutManager has no way to set the number of replicas for the rollouts controller which is required for HA. My understanding is that the RolloutsController supports leader election and multiple pods is supported in an Active-Passive fashion. So while multiple replicas does not benefit performance it is useful for HA purposes for situations like when a node goes down for service
• Note that since this is for HA we need to consider whether to also set anti-affinity by default or support enabling it via field(s) in the RolloutManager 

Why is this important?

• Users expect uninterrupted service from the rollouts controller and multiple replicas are required to achieve this

Scenarios

1. Rollouts controller pod goes down or is unavailable (node failure or maintenance, pod crashes, etc) causing Rollouts not to be processed until controller is active again.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Leader election happens successfully when a controller pod fails

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment