Merge pull request #73140 from SNiemann15/remove_sdn_support

jab-rh · web-flow · commit 44773e02f3d7 · 2024-03-22T12:54:33.000-04:00
[OSDOCS-9223] Remove sdn as supported value
diff --git a/modules/installation-alibaba-config-yaml.adoc b/modules/installation-alibaba-config-yaml.adoc
@@ -58,7 +58,7 @@ sshKey: |
   ssh-rsa AAAA... <7>
 ----
 <1> Required. The installation program prompts you for a cluster name.
-<2> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<2> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <3> Optional. Specify parameters for machine pools that do not define their own platform configuration.
 <4> Required. The installation program prompts you for the region to deploy the cluster to.
 <5> Optional. Specify an existing resource group where the cluster should be installed.
diff --git a/modules/installation-aws-config-yaml.adoc b/modules/installation-aws-config-yaml.adoc
@@ -338,13 +338,13 @@ ifndef::aws-outposts[]
 ====
 The IMDS configuration for control plane machines that is set during cluster installation can only be changed by using the AWS CLI. The IMDS configuration for compute machines can be changed by using compute machine sets.
 ====
-<8> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<8> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 endif::aws-outposts[]
 ifdef::aws-outposts[]
 <6> For compute instances running in an AWS Outpost instance, specify a supported instance type in the AWS Outpost instance.
 <7> For compute instances running in AWS Outpost instance, specify the Availability Zone where the Outpost instance is located.
 <8> For compute instances running in AWS Outpost instance, specify volume type gp2, to avoid using gp3 volume type which is not supported.
-<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <10> If you provide your own VPC, specify subnets for each availability zone that your cluster uses.
 endif::aws-outposts[]
 ifdef::vpc,restricted[]
diff --git a/modules/installation-azure-config-yaml.adoc b/modules/installation-azure-config-yaml.adoc
@@ -232,7 +232,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 //To configure faster storage for etcd, especially for larger clusters, set the
 //storage type as `io1` and set `iops` to `2000`.
 <6> Specify a list of zones to deploy your machines to. For high availability, specify at least two zones.
-<7> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<7> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <8> Optional: A custom {op-system-first} image that should be used to boot control plane and compute machines. The `publisher`, `offer`, `sku`, and `version` parameters under `platform.azure.defaultMachinePlatform.osImage` apply to both control plane and compute machines. If the parameters under `controlPlane.platform.azure.osImage` or `compute.platform.azure.osImage` are set, they override the `platform.azure.defaultMachinePlatform.osImage` parameters.
 <9> Specify the name of the resource group that contains the DNS zone for your base domain.
 <10> Specify the name of an already existing resource group to install your cluster to. If undefined, a new resource group is created for the cluster.
diff --git a/modules/installation-azure-stack-hub-config-yaml.adoc b/modules/installation-azure-stack-hub-config-yaml.adoc
@@ -83,7 +83,7 @@ endif::openshift-origin[]
 <1> The `controlPlane` section is a single mapping, but the `compute` section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Only one control plane pool is used.
 <2> You can specify the size of the disk to use in GB. Minimum recommendation for control plane nodes is 1024 GB.
 <3> Specify the name of the cluster.
-<4> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<4> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <5> Specify the Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
 <6> Specify the name of the resource group that contains the DNS zone for your base domain.
 <7> Specify the name of your Azure Stack Hub local region.
@@ -176,7 +176,7 @@ endif::openshift-origin[]
 <3> The `controlPlane` section is a single mapping, but the `compute` section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the `compute` section must begin with a hyphen, `-`, and the first line of the `controlPlane` section must not. Although both sections currently define a single machine pool, it is possible that future versions of {product-title} will support defining multiple compute pools during installation. Only one control plane pool is used.
 <4> You can specify the size of the disk to use in GB. Minimum recommendation for control plane nodes is 1024 GB.
 <5> The name of the cluster.
-<6> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<6> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <7> The Azure Resource Manager endpoint that your Azure Stack Hub operator provides.
 <8> The name of the resource group that contains the DNS zone for your base domain.
 <9> The name of your Azure Stack Hub local region.
diff --git a/modules/installation-bare-metal-agent-installer-config-yaml.adoc b/modules/installation-bare-metal-agent-installer-config-yaml.adoc
@@ -54,7 +54,7 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,
 ====
 +
 <7> The subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
-<8> The cluster network plugin to install. The supported values are `OVNKubernetes` (default value) and `OpenShiftSDN`.
+<8> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <9> The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.
 <10> You must set the platform to `none` for a single-node cluster. You can set the platform to `vsphere`, `baremetal`, or `none` for multi-node clusters.
 +
diff --git a/modules/installation-bare-metal-config-yaml.adoc b/modules/installation-bare-metal-config-yaml.adoc
@@ -229,7 +229,7 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,
 ====
 +
 <8> The subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
-<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <10> The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.
 <11> You must set the platform to `none`. You cannot provide additional platform configuration variables for
 ifndef::ibm-z,ibm-z-kvm,ibm-power[your platform.]
diff --git a/modules/installation-gcp-config-yaml.adoc b/modules/installation-gcp-config-yaml.adoc
@@ -203,7 +203,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 <6> Optional: The custom encryption key section to encrypt both virtual machines and persistent volumes. Your default compute service account must have the permissions granted to use your KMS key and have the correct IAM role assigned. The default service account name follows the `service-<project_number>@compute-system.iam.gserviceaccount.com` pattern. For more information about granting the correct permissions for your service account, see "Machine management" -> "Creating compute machine sets" -> "Creating a compute machine set on GCP".
 <7> Optional: A set of network tags to apply to the control plane or compute machine sets. The `platform.gcp.defaultMachinePlatform.tags` parameter will apply to both control plane and compute machines. If the `compute.platform.gcp.tags` or `controlPlane.platform.gcp.tags` parameters are set, they override the `platform.gcp.defaultMachinePlatform.tags` parameter.
 <8> Optional: A custom {op-system-first} that should be used to boot control plane and compute machines. The `project` and `name` parameters under `platform.gcp.defaultMachinePlatform.osImage` apply to both control plane and compute machines. If the `project` and `name` parameters under `controlPlane.platform.gcp.osImage` or `compute.platform.gcp.osImage` are set, they override the `platform.gcp.defaultMachinePlatform.osImage` parameters.
-<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 ifdef::vpc,restricted[]
 <10> Specify the name of an existing VPC.
 <11> Specify the name of the existing subnet to deploy the control plane machines to. The subnet must belong to the VPC that you specified.
diff --git a/modules/installation-gcp-user-infra-shared-vpc-config-yaml.adoc b/modules/installation-gcp-user-infra-shared-vpc-config-yaml.adoc
@@ -82,7 +82,7 @@ endif::openshift-origin[]
 If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance. Use larger machine types, such as `n1-standard-8`, for your machines if you disable simultaneous multithreading.
 ====
 <5> Optional: A set of network tags to apply to the control plane or compute machine sets. The `platform.gcp.defaultMachinePlatform.tags` parameter applies to both control plane and compute machines. If the `compute.platform.gcp.tags` or `controlPlane.platform.gcp.tags` parameters are set, they override the `platform.gcp.defaultMachinePlatform.tags` parameter.
-<6> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<6> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <7> Specify the main project where the VM instances reside.
 <8> Specify the region that your VPC network is in.
 ifndef::openshift-origin[]
diff --git a/modules/installation-ibm-cloud-config-yaml.adoc b/modules/installation-ibm-cloud-config-yaml.adoc
@@ -89,7 +89,7 @@ endif::openshift-origin[]
 ====
 If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance. Use larger machine types, such as `n1-standard-8`, for your machines if you disable simultaneous multithreading.
 ====
-<5> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<5> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 ifndef::openshift-origin[]
 <6> Enables or disables FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
 +
@@ -172,7 +172,7 @@ endif::openshift-origin[]
 If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance. Use larger machine types, such as `n1-standard-8`, for your machines if you disable simultaneous multithreading.
 ====
 <5> The machine CIDR must contain the subnets for the compute machines and control plane machines.
-<6> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<6> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <7> The name of an existing resource group. All installer-provisioned cluster resources are deployed to this resource group. If undefined, a new resource group is created for the cluster.
 <8> Specify the name of the resource group that contains the existing virtual private cloud (VPC). The existing VPC and subnets should be in this resource group. The cluster will be installed to this VPC.
 <9> Specify the name of an existing VPC.
@@ -261,7 +261,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 ====
 <5> The machine CIDR must contain the subnets for the compute machines and control plane machines.
 <6> The CIDR must contain the subnets defined in `platform.ibmcloud.controlPlaneSubnets` and `platform.ibmcloud.computeSubnets`.
-<7> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<7> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <8> The name of an existing resource group. All installer-provisioned cluster resources are deployed to this resource group. If undefined, a new resource group is created for the cluster.
 <9> Specify the name of the resource group that contains the existing virtual private cloud (VPC). The existing VPC and subnets should be in this resource group. The cluster will be installed to this VPC.
 <10> Specify the name of an existing VPC.
@@ -393,7 +393,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 ====
 <5> The machine CIDR must contain the subnets for the compute machines and control plane machines.
 <6> The CIDR must contain the subnets defined in `platform.ibmcloud.controlPlaneSubnets` and `platform.ibmcloud.computeSubnets`.
-<7> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<7> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <8> The name of an existing resource group. All installer-provisioned cluster resources are deployed to this resource group. If undefined, a new resource group is created for the cluster.
 <9> Based on the network restrictions of the VPC, specify alternate service endpoints as needed. This overrides the default public endpoint for the service.
 <10> Specify the name of the resource group that contains the existing virtual private cloud (VPC). The existing VPC and subnets should be in this resource group. The cluster will be installed to this VPC.
diff --git a/modules/installation-ibm-power-vs-config-yaml.adoc b/modules/installation-ibm-power-vs-config-yaml.adoc
@@ -97,7 +97,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning a
 ====
 When simultaneous multithreading (SMT), or hyperthreading is not enabled, one vCPU is equivalent to one physical core. When enabled, total vCPUs is computed as: (Thread(s) per core * Core(s) per socket) * Socket(s). The smtLevel controls the threads per core. Lower SMT levels may require additional assigned cores when deploying the cluster nodes. You can do this by setting the `'processors'` parameter in the `install-config.yaml` file to an appropriate value to meet the requirements for deploying {product-title} successfully.
 ====
-<5> The cluster network plugin to install. The supported value is `OVNKubernetes`.
+<5> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <6> The name of an existing resource group.
 <7> Required. The installation program prompts you for this value.
 ifdef::openshift-origin[]
@@ -168,7 +168,7 @@ sshKey: ssh-ed25519 AAAA... <10>
 When simultaneous multithreading (SMT), or hyperthreading is not enabled, one vCPU is equivalent to one physical core. When enabled, total vCPUs is computed as (Thread(s) per core * Core(s) per socket) * Socket(s). The smtLevel controls the threads per core. Lower SMT levels may require additional assigned cores when deploying the cluster nodes. You can do this by setting the `'processors'` parameter in the `install-config.yaml` file to an appropriate value to meet the requirements for deploying {product-title} successfully.
 ====
 <5> The machine CIDR must contain the subnets for the compute machines and control plane machines.
-<6> The cluster network plugin to install. The supported value is `OVNKubernetes`.
+<6> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <7> Specify the name of an existing VPC.
 <8> Specify how to publish the user-facing endpoints of your cluster. Set publish to `Internal` to deploy a private cluster.
 <9> Required. The installation program prompts you for this value.
@@ -364,7 +364,7 @@ When simultaneous multithreading (SMT), or hyperthreading is not enabled, one vC
 ====
 <6> The machine CIDR must contain the subnets for the compute machines and control plane machines.
 <7> The CIDR must contain the subnets defined in `platform.ibmcloud.controlPlaneSubnets` and `platform.ibmcloud.computeSubnets`.
-<8> The cluster network plugin to install. The supported value is `OVNKubernetes`.
+<8> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <9> The name of an existing resource group. The existing VPC and subnets should be in this resource group. The cluster is deployed to this resource group.
 <10> Specify the name of an existing VPC.
 <11> Specify the name of the existing VPC subnet. The subnets must belong to the VPC that you specified. Specify a subnet for each availability zone in the region.
diff --git a/modules/installation-installer-provisioned-vsphere-config-yaml.adoc b/modules/installation-installer-provisioned-vsphere-config-yaml.adoc
@@ -105,7 +105,7 @@ endif::restricted[]
 <3> The cluster name that you specified in your DNS records.
 <4> Optional: Provides additional configuration for the machine pool parameters for the compute and control plane machines.
 <5> Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a `datastore` object. A failure domain defines the vCenter location for {product-title} cluster nodes.
-<6> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images. 
+<6> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
 +
 [IMPORTANT]
 ====
@@ -116,7 +116,7 @@ If you must specify VMs across multiple datastores, use a `datastore` object to
 <7> Optional: Provides an existing resource pool for machine creation. If you do not specify a value, the installation program uses the root resource pool of the vSphere cluster.
 <8> The vSphere disk provisioning method.
 ifdef::network[]
-<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
+<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 endif::network[]
 ifdef::restricted[]
 <9> The location of the {op-system-first} image that is accessible from the bastion server.
diff --git a/modules/installation-nutanix-config-yaml.adoc b/modules/installation-nutanix-config-yaml.adoc
diff --git a/modules/installation-user-defined-tags-azure.adoc b/modules/installation-user-defined-tags-azure.adoc
diff --git a/modules/installing-ocp-agent-inputs.adoc b/modules/installing-ocp-agent-inputs.adoc

Original file line number	Diff line number	Diff line change
`@@ -54,7 +54,7 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,`
`54`	`54`	`====`
`55`	`55`	`+`
`56`	`56`	<7> The subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
`57`		-<8> The cluster network plugin to install. The supported values are `OVNKubernetes` (default value) and `OpenShiftSDN`.
	`57`	+<8> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
`58`	`58`	`<9> The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.`
`59`	`59`	<10> You must set the platform to `none` for a single-node cluster. You can set the platform to `vsphere`, `baremetal`, or `none` for multi-node clusters.
`60`	`60`	`+`
Original file line number	Diff line number	Diff line change
`@@ -229,7 +229,7 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,`
`229`	`229`	`====`
`230`	`230`	`+`
`231`	`231`	<8> The subnet prefix length to assign to each individual node. For example, if `hostPrefix` is set to `23`, then each node is assigned a `/23` subnet out of the given `cidr`, which allows for 510 (2^(32 - 23) - 2) pod IP addresses. If you are required to provide access to nodes from an external network, configure load balancers and routers to manage the traffic.
`232`		-<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
	`232`	+<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
`233`	`233`	`<10> The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.`
`234`	`234`	<11> You must set the platform to `none`. You cannot provide additional platform configuration variables for
`235`	`235`	`ifndef::ibm-z,ibm-z-kvm,ibm-power[your platform.]`