Skip to content

Commit d3c3024

Browse files
jeana-redhatjeana-redhat
authored
Merge pull request #75717 from dfitzmau/OSDOCS-10463
OSDOCS-10463: vsphere multiple subnets
2 parents 53581c8 + 5abcf7e commit d3c3024

File tree

4 files changed

+102
-7
lines changed

4 files changed

+102
-7
lines changed

‎installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-network-customizations.adoc

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,11 +60,24 @@ include::modules/ipi-install-modifying-install-config-for-dual-stack-network.ado
6060

6161
include::modules/configuring-vsphere-regions-zones.adoc[leveloffset=+2]
6262

63-
// begin network customization
63+
// Network configuration phases
6464
include::modules/nw-network-config.adoc[leveloffset=+1]
65+
66+
// Specifying advanced network configuration
6567
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
68+
69+
// Specifying multiple subnets for your network
70+
include::modules/nw-operator-vsphere-multiple-subnets.adoc[leveloffset=+2]
71+
72+
[role="_additional-resources"]
73+
.Additional resources
74+
75+
* xref:../../../installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-network-customizations.adoc#nw-operator-cr_installing-vsphere-installer-provisioned-network-customizations[Cluster Network Operator configuration]
76+
77+
* xref:../../../rest_api/config_apis/infrastructure-config-openshift-io-v1.adoc#spec-platformspec-vsphere-nodenetworking[`.spec.platformSpec.vsphere.nodeNetworking`]
78+
79+
// Cluster Network Operator configuration
6680
include::modules/nw-operator-cr.adoc[leveloffset=+1]
67-
// end network customization
6881

6982
// Services for a user-managed load balancer
7083
include::modules/nw-osp-services-external-load-balancer.adoc[leveloffset=+1]

‎installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,9 +61,23 @@ include::modules/installation-configure-proxy.adoc[leveloffset=+2]
6161

6262
include::modules/configuring-vsphere-regions-zones.adoc[leveloffset=+2]
6363

64-
// Network Operator specific configuration
64+
// Network configuration phases
6565
include::modules/nw-network-config.adoc[leveloffset=+1]
66+
67+
// Specifying advanced network configuration
6668
include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
69+
70+
// Specifying multiple subnets for your network
71+
include::modules/nw-operator-vsphere-multiple-subnets.adoc[leveloffset=+2]
72+
73+
[role="_additional-resources"]
74+
.Additional resources
75+
76+
* xref:../../../installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc#nw-operator-cr_installing-vsphere-network-customizations[Cluster Network Operator configuration]
77+
78+
* xref:../../../rest_api/config_apis/infrastructure-config-openshift-io-v1.adoc#spec-platformspec-vsphere-nodenetworking[`.spec.platformSpec.vsphere.nodeNetworking`]
79+
80+
// Cluster Network Operator configuration
6781
include::modules/nw-operator-cr.adoc[leveloffset=+1]
6882

6983
include::modules/installation-generate-ignition-configs.adoc[leveloffset=+1]

‎modules/nw-network-config.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,18 +25,18 @@ Phase 1:: You can customize the following network-related fields in the `install
2525
* `networking.serviceNetwork`
2626
* `networking.machineNetwork`
2727
+
28-
For more information on these fields, refer to _Installation configuration parameters_.
28+
For more information, see "Installation configuration parameters".
2929
+
3030
[NOTE]
3131
====
32-
Set the `networking.machineNetwork` to match the CIDR that the preferred NIC resides in.
32+
Set the `networking.machineNetwork` to match the Classless Inter-Domain Routing (CIDR) where the preferred subnet is located.
3333
====
3434
+
3535
[IMPORTANT]
3636
====
37-
The CIDR range `172.17.0.0/16` is reserved by libVirt. You cannot use this range or any range that overlaps with this range for any networks in your cluster.
37+
The CIDR range `172.17.0.0/16` is reserved by `libVirt`. You cannot use any other CIDR range that overlaps with the `172.17.0.0/16` CIDR range for networks in your cluster.
3838
====
3939

4040
Phase 2:: After creating the manifest files by running `openshift-install create manifests`, you can define a customized Cluster Network Operator manifest with only the fields you want to modify. You can use the manifest to specify advanced network configuration.
4141

42-
You cannot override the values specified in phase 1 in the `install-config.yaml` file during phase 2. However, you can further customize the network plugin during phase 2.
42+
During phase 2, you cannot override the values that you specified in phase 1 in the `install-config.yaml` file. However, you can customize the network plugin during phase 2.

‎modules/nw-operator-vsphere-multiple-subnets.adoc

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned-network-customizations.adoc
4+
// * installing/installing_vsphere/upi/installing-vsphere-network-customizations.adoc
5+
6+
:_mod-docs-content-type: PROCEDURE
7+
[id="nw-operator-vsphere-multiple-subnets_{context}"]
8+
= Specifying multiple subnets for your network
9+
10+
Before you install an {product-title} cluster on a {vmw-short} host, you can specify multiple subnets for a networking implementation so that the {vmw-short} cloud controller manager (CCM) can select the appropriate subnet for a given networking situation. {vmw-short} can use the subnet for managing pods and services on your cluster.
11+
12+
For this configuration, you must specify internal and external Classless Inter-Domain Routing (CIDR) implementations in the {vmw-short} CCM configuration. Each CIDR implementation lists an IP address range that the CCM uses to decide what subnets interact with traffic from internal and external networks.
13+
14+
[IMPORTANT]
15+
====
16+
Failure to configure internal and external CIDR implementations in the {vmw-short} CCM configuration can cause the {vmw-short} CCM to select the wrong subnet. This situation causes the following error:
17+
18+
----
19+
ERROR Bootstrap failed to complete: timed out waiting for the condition
20+
ERROR Failed to wait for bootstrapping to complete. This error usually happens when there is a problem with control plane hosts that prevents the control plane operators from creating the control plane.
21+
----
22+
23+
This configuration can cause new nodes that associate with a `MachineSet` object with a single subnet to become unusable as each new node receives the `node.cloudprovider.kubernetes.io/uninitialized` taint. These situations can cause communication issues with the Kubernetes API server that can cause installation of the cluster to fail.
24+
====
25+
26+
.Prerequisites
27+
28+
* You created Kubernetes manifest files for your {product-title} cluster.
29+
30+
.Procedure
31+
32+
. From the directory where you store your {product-title} cluster manifest files, open the `manifests/cluster-infrastructure-02-config.yml` manifest file.
33+
34+
. Add a `nodeNetworking` object to the file and specify internal and external network subnet CIDR implementations for the object.
35+
+
36+
[TIP]
37+
====
38+
For most networking situations, consider setting the standard multiple-subnet configuration. This configuration requires that you set the same IP address ranges in the `nodeNetworking.internal.networkSubnetCidr` and `nodeNetworking.external.networkSubnetCidr` parameters.
39+
====
40+
+
41+
.Example of a configured `cluster-infrastructure-02-config.yml` manifest file
42+
[source,yaml]
43+
----
44+
apiVersion: config.openshift.io/v1
45+
kind: Infrastructure
46+
metadata:
47+
name: cluster
48+
spec:
49+
cloudConfig:
50+
key: config
51+
name: cloud-provider-config
52+
platformSpec:
53+
type: VSphere
54+
vsphere:
55+
failureDomains:
56+
- name: generated-failure-domain
57+
...
58+
nodeNetworking:
59+
external:
60+
networkSubnetCidr:
61+
- <machine_network_cidr_ipv4>
62+
- <machine_network_cidr_ipv6>
63+
internal:
64+
networkSubnetCidr:
65+
- <machine_network_cidr_ipv4>
66+
- <machine_network_cidr_ipv6>
67+
# ...
68+
----

0 commit comments

Comments
 (0)