openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-17805 GA for Azure outboundType NAT Gateways

Browse Source
This commit is contained in:
Ben Scott
2026-01-12 14:24:02 -05:00
committed by openshift-cherrypick-robot
parent 36ea5c268f
commit 3351596426
1 changed files with 16 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
modules/installation-configuration-parameters.adoc
View File

@@ -2394,18 +2394,16 @@ Supplying more than one user-assigned identity is an experimental feature, which
|platform:
azure:
outboundType:
|The outbound routing strategy used to connect your cluster to the internet. If you are using user-defined routing, you must have pre-existing networking available. The outbound routing must be configured before installing a cluster. The installation program does not configure user-defined routing. If you specify the `NatGateway` routing strategy, the installation program only creates one NAT gateway. If you specify the `NatGateway` routing strategy, your account must have the `Microsoft.Network/natGateways/read` and `Microsoft.Network/natGateways/write` permissions.
|The outbound routing strategy used to connect your cluster to the internet. The following strategies are available:
[IMPORTANT]
====
[subs="attributes+"]
`NatGateway` is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
`UserDefinedRouting`:: Specifies to the installation program that you will provide and configure your own networking infrastructure for outbound access. The outbound routing must be configured before installing a cluster. The installation program does not configure user-defined routing.
`LoadBalancer`:: Specifies that a single load balancer will be provisioned to provide outbound access for your cluster. This is the default value.
`NATGatewaySingleZone`:: Specifies that the installation program will create one NAT Gateway. If you provide your own subnets via the `platform.azure.subnets` parameter, the installation program will attach the NAT Gateway to the compute subnet you specify. If you do not provide your own subnets, the installation program will create a subnet for the control plane and a subnet for the compute plane, and attach the NAT Gateway to the compute subnet.
`NATGatewayMultiZone`:: Specifies that the installation program will create multiple NAT Gateways. If you provide your own subnets via the `platform.azure.subnets` parameter, the installation program creates a NAT Gateway for each subnet with the `node` role, assigns a zone to each NAT Gateway, and associates a NAT Gateway to each subnet. If you do not provide your own subnets, the installation program creates a compute subnet and NAT Gateway for each zone in the region, then attaches them to each other.
For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
====
//You can't put a snippet within a conditional.
If you specify either the `NATGatewaySingleZone` or the `NATGatewayMultiZone` routing strategy, your account must have the `Microsoft.Network/natGateways/read` and `Microsoft.Network/natGateways/write` permissions. NAT Gateways can only be used for compute machines.
*Value:* `LoadBalancer`, `UserDefinedRouting`, or `NatGateway`. The default is `LoadBalancer`.
*Value:* `LoadBalancer`, `UserDefinedRouting`, `NATGatewaySingleZone`, or `NATGatewayMultiZone`. The default is `LoadBalancer`.
|platform:
azure:
@@ -2414,6 +2412,15 @@ For more information about the support scope of Red Hat Technology Preview featu
*Value:* Any valid region name, such as `centralus`.
|platform:
azure:
subnets:
- name:
role:
|A list of one or more pairs of parameters which specify the name and role of a pre-existing subnet. The installation program will use the provided subnets for the specified roles. You can only specify one subnet with the `control-plane` role. If you specify pre-existing subnets, you must also set the `platform.azure.networkResourceGroupName` and `platform.azure.virtualNetwork` parameters. Pre-existing subnets that you provide must use the same region as you specified in the `platform.azure.region` parameter. If you use the `NATGatewaySingleZone` outbound routing strategy, you can only specify one subnet with the `node` role.
*Value:* `name` specifies the name of the subnet. Valid `role` values are `node` or `control-plane`.
|platform:
azure:
zone: