You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-installation-workflow[Deploying with dual-stack networking].
20
+
* See xref:../../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-installation-workflow[Configuring the install-config yaml file].
20
21
* See xref:../../installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc#installation-three-node-cluster_installing-restricted-networks-bare-metal[Configuring a three-node cluster] to deploy three-node clusters in bare metal environments.
21
22
* See xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#root-device-hints_preparing-to-install-with-agent-based-installer[About root device hints].
22
23
* See link:https://nmstate.io/examples.html[NMState state examples].
Copy file name to clipboardExpand all lines: modules/installation-bare-metal-agent-installer-config-yaml.adoc
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,41 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,
76
76
<9> The cluster network provider Container Network Interface (CNI) plug-in to install. The supported values are `OVNKubernetes` (default value) and `OpenShiftSDN` .
77
77
<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.
78
78
<11> You must set the platform to `none` for a single-node cluster. You can also set the platform to `vSphere` and `baremetal`.
79
+
+
80
+
[NOTE]
81
+
====
82
+
If you set the platform to `vSphere` or `baremetal`, you can configure IP address endpoints for cluster nodes in three ways:
83
+
84
+
* IPv4
85
+
* IPv6
86
+
* IPv4 and IPv6 in parallel (dual-stack)
87
+
88
+
.Example of dual-stack networking
89
+
[source,yaml]
90
+
----
91
+
networking:
92
+
clusterNetwork:
93
+
- cidr: 172.21.0.0/16
94
+
hostPrefix: 23
95
+
- cidr: fd02::/48
96
+
hostPrefix: 64
97
+
machineNetwork:
98
+
- cidr: 192.168.11.0/16
99
+
- cidr: 2001:DB8::/32
100
+
serviceNetwork:
101
+
- 172.22.0.0/16
102
+
- fd03::/112
103
+
networkType: OVNKubernetes
104
+
platform:
105
+
baremetal:
106
+
apiVIPs:
107
+
- 192.168.11.3
108
+
- 2001:DB8::4
109
+
ingressVIPs:
110
+
- 192.168.11.4
111
+
- 2001:DB8::5
112
+
----
113
+
====
79
114
<12> Whether to enable or disable 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.
Copy file name to clipboardExpand all lines: modules/installing-ocp-agent.adoc
+70-1Lines changed: 70 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,6 +83,42 @@ sshKey: |
83
83
<2> Enter your pull secret.
84
84
<3> Enter your ssh public key.
85
85
86
+
+
87
+
[NOTE]
88
+
====
89
+
If you set the platform to `vSphere` or `baremetal`, you can configure IP address endpoints for cluster nodes in three ways:
90
+
91
+
* IPv4
92
+
* IPv6
93
+
* IPv4 and IPv6 in parallel (dual-stack)
94
+
95
+
.Example of dual-stack networking
96
+
[source,yaml]
97
+
----
98
+
networking:
99
+
clusterNetwork:
100
+
- cidr: 172.21.0.0/16
101
+
hostPrefix: 23
102
+
- cidr: fd02::/48
103
+
hostPrefix: 64
104
+
machineNetwork:
105
+
- cidr: 192.168.11.0/16
106
+
- cidr: 2001:DB8::/32
107
+
serviceNetwork:
108
+
- 172.22.0.0/16
109
+
- fd03::/112
110
+
networkType: OVNKubernetes
111
+
platform:
112
+
baremetal:
113
+
apiVIPs:
114
+
- 192.168.11.3
115
+
- 2001:DB8::4
116
+
ingressVIPs:
117
+
- 192.168.11.4
118
+
- 2001:DB8::5
119
+
----
120
+
====
121
+
86
122
. Create the `agent-config.yaml` file:
87
123
+
88
124
[source,yaml]
@@ -133,7 +169,6 @@ the number of hosts defined is 3. When 3 master nodes and 2 worker nodes are def
133
169
<4> The `rootDeviceHints` parameter enables provisioning of the Red Hat Enterprise Linux CoreOS (RHCOS) image to a particular device. It examines the devices in the order it discovers them, and compares the discovered values with the hint values. It uses the first discovered device that matches the hint value.
134
170
<5> Set this optional parameter to configure the network interface of a host in NMState format.
135
171
136
-
137
172
+
138
173
. Create the Agent image by running the following command:
139
174
+
@@ -198,3 +233,37 @@ INFO To access the cluster as the system:admin user when using 'oc', run
198
233
INFO export KUBECONFIG=/home/core/installer/auth/kubeconfig
199
234
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.sno-cluster.test.example.com
200
235
----
236
+
237
+
238
+
[NOTE]
239
+
====
240
+
If you are using the optional method of ZTP manifests, you can configure IP address endpoints for cluster nodes through the `AgentClusterInstall.yaml` file in three ways:
0 commit comments