Merge pull request #80993 from alishaIBM/ipi_capi

OCP 4.17: IBM Power Virtual Server using installer-provisioned infras…

Author: ShaunaDiaz

modules/installation-about-restricted-network.adoc

@@ -26,6 +26,7 @@ ifeval::["{context}" == "installing-ibm-cloud-restricted"]
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-ibm-power-vs"]
 :ipi:
+:ipi-powervs:
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-gcp-installer-provisioned"]
 :ipi:
@@ -53,6 +54,13 @@ endif::[]
 In {product-title} {product-version}, you can perform an installation that does not
 require an active connection to the internet to obtain software components. Restricted network installations can be completed using installer-provisioned infrastructure or user-provisioned infrastructure, depending on the cloud platform to which you are installing the cluster.
 
+ifdef::ipi-powervs[]
+[NOTE]
+====
+For installer-provisioned infrastructure in {product-title} {product-version}, you need to deploy your restricted network cluster in {product-title} 4.16 and upgrade it to {product-title} {product-version}.
+====
+endif::ipi-powervs[]
+
 ifndef::ibm-power,ibm-cloud[]
 If you choose to perform a restricted network installation on a cloud platform, you
 still require access to its cloud APIs. Some cloud functions, like
@@ -146,6 +154,7 @@ ifeval::["{context}" == "installing-ibm-cloud-restricted"]
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-ibm-power-vs"]
 :!ipi:
+:!ipi-powervs:
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-gcp-installer-provisioned"]
 :!ipi:

modules/installation-ibm-cloud-regions.adoc

@@ -65,7 +65,14 @@ ifdef::ibm-power-vs[]
 ** `wdc06`
 ** `wdc07`
 
-You might optionally specify the {ibm-cloud-name} region in which the installer will create any VPC components. Supported regions in {ibm-cloud-name} are:
+You might optionally specify the {ibm-cloud-name} region in which the installation program creates any VPC components.
+
+[NOTE]
+====
+If you do not specify the region, the installation program selects the region closest to {ibm-power-server-title} zone you are deploying to.
+====
+
+{ibm-cloud-name} supports the following regions:
 
 * `us-south`
 * `eu-de`

modules/installation-ibm-power-vs-config-yaml.adoc

@@ -149,8 +149,6 @@ platform:
     powervsResourceGroup: "ibmcloud-resource-group"
     region: powervs-region
     vpcName: name-of-existing-vpc <7>
-    vpcSubnets:
-    - powervs-region-example-subnet-1
     vpcRegion : vpc-region
     zone: powervs-zone
     serviceInstanceGUID: "powervs-region-service-instance-guid"
@@ -238,15 +236,13 @@ platform:
     region: powervs-region
     vpcRegion : vpc-region
     vpcName: name-of-existing-vpc <7>
-    vpcSubnets: <8>
-    - powervs-region-example-subnet-1
     zone: powervs-zone
     serviceInstanceGUID: "powervs-region-service-instance-guid"
 credentialsMode: Manual
-publish: External <9>
-pullSecret: '{"auths": ...}' <10>
+publish: External <8>
+pullSecret: '{"auths": ...}' <9>
 fips: false
-sshKey: ssh-ed25519 AAAA... <11>
+sshKey: ssh-ed25519 AAAA... <10>
 ----
 <1> If you do not provide these parameters and values, the installation program provides the default value.
 <2> 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. Both sections currently define a single machine pool. Only one control plane pool is used.
@@ -260,10 +256,9 @@ When simultaneous multithreading (SMT), or hyperthreading is not enabled, one vC
 <5> The machine CIDR must contain the subnets for the compute machines and control plane machines.
 <6> The cluster network plugin for installation. The supported value is `OVNKubernetes`.
 <7> Specify the name of an existing VPC.
-<8> 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.
-<9> Specify how to publish the user-facing endpoints of your cluster.
-<10> Required. The installation program prompts you for this value.
-<11> Provide the `sshKey` value that you use to access the machines in your cluster.
+<8> Specify how to publish the user-facing endpoints of your cluster.
+<9> Required. The installation program prompts you for this value.
+<10> Provide the `sshKey` value that you use to access the machines in your cluster.
 +
 [IMPORTANT]
 ====

modules/installation-initializing.adoc

@@ -106,6 +106,9 @@ endif::[]
 ifeval::["{context}" == "installing-ibm-power-vs-customizations"]
 :ibm-power-vs:
 endif::[]
+ifeval::["{context}" == "installing-ibm-powervs-vpc"]
+:ibm-power-vs:
+endif::[]
 ifeval::["{context}" == "installing-restricted-networks-ibm-power-vs"]
 :ibm-power-vs:
 :restricted:
@@ -243,7 +246,9 @@ $ ./openshift-install create install-config --dir <installation_directory> <1>
 files that the installation program creates.
 +
 When specifying the directory:
+ifndef::ibm-power-vs[]
 * Verify that the directory has the `execute` permission. This permission is required to run Terraform binaries under the installation directory.
+endif::ibm-power-vs[]
 * Use an empty directory. Some installation assets, such as bootstrap X.509 certificates, have short expiration intervals, therefore you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier {product-title} version.
 ifdef::ibm-power-vs[]
 +
@@ -699,6 +704,9 @@ endif::[]
 ifeval::["{context}" == "installing-ibm-power-vs-customizations"]
 :!ibm-power-vs:
 endif::[]
+ifeval::["{context}" == "installing-ibm-powervs-vpc"]
+:!ibm-power-vs:
+endif::[]
 ifeval::["{context}" == "installing-restricted-networks-ibm-power-vs"]
 :!ibm-power-vs:
 :!restricted:

modules/quotas-and-limits-ibm-power-vs.adoc

@@ -37,11 +37,6 @@ Each {product-title} cluster creates its own Transit Gateway to enable communica
 
 There is a limit of one Dynamic Host Configuration Protocol (DHCP) service per {ibm-power-server-name} instance.
 
-[discrete]
-== Networking
-
-Due to networking limitations, there is a restriction of one OpenShift cluster installed through IPI per zone per account. This is not configurable.
-
 [discrete]
 == Virtual Server Instances