Feature Overview:

• Expose the Azure setting disableOutboundSNAT to the install-config

Goals:

• Scaling past the 59 worker node limit on private clusters with a LoadBalancer outbound type

Requirements:

• Ability to set disableOutboundSNAT in the install-config
• Adding additional IP addresses to the outbound rule rather than using the default

Use Cases:

• Customers need to be able to scale their clusters past 59 nodes without IP address exhaustion or lowering the number of SNAT ports per VM

Questions to Answer:

• None

Out of Scope

• Create an OpenShift component which manages this on behalf of the customer

Background:

• https://docs.google.com/document/d/1sG_kHhgESpqOaHuJdX9a2Pq6YGYJeL-H8xPwNlIDgbk
• https://docs.google.com/document/d/1g7MYmXhtkNy7ueuX7L-dXIDTokH3pc7puvvvGMX6XzA/edit#heading=h.54u5s56qhxwd
• https://learn.microsoft.com/en-us/azure/load-balancer/outbound-rules#preventoutbound

Customer Considerations:

• None

Documentation Considerations:

• Document how to configure disableOutboundSNAT and how to use it

Interoperability Considerations:

• None