Feature Overview (aka. Goal Summary)  

Provide the capability to dynamically scale ingress router pods based on node role.

Goals (aka. expected user outcomes)

• Create a method of using a label selector to make the ingress router pod count match the number of nodes with a specific label.
  • For example, add an option in the IngressController CR to place router pods on specific nodes (based upon an "autoscale" option) and scale the count of router pods deployed based upon the count of matching nodes. 
  • As a specific alternative, create a method to make the ingress router pod count match the number of Availability Zones (AWS).
• Expose setting of the replica count for ingress router pods via the install-config

Requirements (aka. Acceptance Criteria):

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.{color}

Use Cases (Optional):

Questions to Answer (Optional):

Out of Scope

Background

Service Delivery needs this for OSD and ROSA clusters. See https://issues.redhat.com/browse/NE-361

Customer Considerations

• https://docs.google.com/document/d/15ZiSzbszPUScU3_SfwsIBWiyzBjsGifCYsPU3hxyHlw/edit#heading=h.bupciudrwmna
•  

Documentation Considerations

Interoperability Considerations

Affected packages:

• IngressController
• cluster-ingress-operator