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
You must use DHCP for the network and ensure that the DHCP server is configured to provide persistent IP addresses and host names to the cluster machines.
75
-
Additionally, you must create the following networking resources before you install the {product-title} cluster:
74
+
You must use DHCP for the network and ensure that the DHCP server is configured to provide persistent IP addresses to the cluster machines. Additionally, you must create the following networking resources before you install the {product-title} cluster:
You must create DNS records for two static IP addresses in the appropriate DNS server for the vCenter instance that hosts your {product-title} cluster. In each record, `<cluster_name>` is the cluster name and `<base_domain>` is the cluster base domain that you specify when you install the cluster. A complete DNS record takes the form: `<component>.<cluster_name>.<base_domain>.`.
Before you install a cluster that contains user-provisioned infrastructure on
11
-
VMware vSphere, you must create {op-system} machines on vSphere hosts for it to
12
-
use.
10
+
Before you install a cluster that contains user-provisioned infrastructure on VMware vSphere, you must create {op-system} machines on vSphere hosts for it to use.
13
11
14
12
.Prerequisites
15
13
16
14
* Obtain the Ignition config files for your cluster.
17
-
* Have access to an HTTP server that you can access from your computer and that
18
-
the machines that you create can access.
15
+
* Have access to an HTTP server that you can access from your computer and that the machines that you create can access.
19
16
* Create a link:https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vcenterhost.doc/GUID-B1018F28-3F14-4DFE-9B4B-F48BBDB72C10.html[vSphere cluster].
20
17
21
18
.Procedure
22
19
23
-
. Upload the bootstrap Ignition config file, which is named
24
-
`<installation_directory>/bootstrap.ign`, that the installation program created
25
-
to your HTTP server. Note the URL of this file.
26
-
+
27
-
You must host the bootstrap Ignition config file because it is too large to
28
-
fit in a vApp property.
20
+
. Convert the control plane, compute, and bootstrap Ignition config files to Base64 encoding.
29
21
30
-
. Save the following secondary Ignition config file for your bootstrap node to
31
-
your computer as `<installation_directory>/append-bootstrap.ign`.
32
22
+
33
-
ifndef::openshift-origin[]
34
-
----
35
-
{
36
-
"ignition": {
37
-
"config": {
38
-
"merge": [
39
-
{
40
-
"source": "<bootstrap_ignition_config_url>" <1>
41
-
}
42
-
]
43
-
},
44
-
"version": "3.1.0"
45
-
}
46
-
}
47
-
----
48
-
endif::openshift-origin[]
49
-
ifdef::openshift-origin[]
50
-
----
51
-
{
52
-
"ignition": {
53
-
"config": {
54
-
"merge": [
55
-
{
56
-
"source": "<bootstrap_ignition_config_url>", <1>
57
-
"verification": {}
58
-
}
59
-
]
60
-
},
61
-
"timeouts": {},
62
-
"version": "3.0.0"
63
-
},
64
-
"networkd": {},
65
-
"passwd": {},
66
-
"storage": {},
67
-
"systemd": {}
68
-
}
69
-
----
70
-
endif::openshift-origin[]
71
-
<1> Specify the URL of the bootstrap Ignition config file that you hosted.
72
-
+
73
-
When you create the virtual machine (VM) for the bootstrap machine, you use
74
-
this Ignition config file.
75
-
76
-
. Convert the master, worker, and secondary bootstrap Ignition config files to base64
77
-
encoding.
78
-
+
79
-
For example, if you use a Linux operating system, you can use the `base64`
80
-
command to encode the files.
23
+
For example, if you use a Linux operating system, you can use the `base64` command to encode the files.
. Obtain the {op-system} OVA image from the link:https://access.redhat.com/downloads/content/290[Product Downloads] page on the Red Hat Customer Portal or the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/[{op-system} image mirror] page.
109
47
+
110
48
[IMPORTANT]
111
49
====
112
-
The {op-system} images might not change with every release of {product-title}.
113
-
You must download an image with the highest version that is
114
-
less than or equal to the {product-title} version that you install. Use the image version
115
-
that matches your {product-title} version if it is available.
50
+
The {op-system} images might not change with every release of {product-title}. You must download an image with the highest version that is less than or equal to the {product-title} version that you install. Use the image version that matches your {product-title} version if it is available.
116
51
====
117
52
+
118
-
The file name contains the {product-title} version number in the format
119
-
`rhcos-<version>-vmware.<architecture>.ova`.
53
+
The filename contains the {product-title} version number in the format `rhcos-<version>-vmware.<architecture>.ova`.
. Obtain the {op-system} images from the link:https://getfedora.org/en/coreos/download?tab=metal_virtualized&stream=stable[{op-system} Downloads] page
124
57
endif::openshift-origin[]
125
58
126
59
. In the vSphere Client, create a folder in your datacenter to store your VMs.
@@ -133,25 +66,17 @@ endif::openshift-origin[]
133
66
+
134
67
[NOTE]
135
68
====
136
-
In the following steps, you use the same template for all of your cluster
137
-
machines and provide the location for the Ignition config file for that machine
138
-
type when you provision the VMs.
69
+
In the following steps, you use the same template for all of your cluster machines and provide the location for the Ignition config file for that machine type when you provision the VMs.
139
70
====
140
-
.. From the *Hosts and Clusters* tab, right-click your cluster's name and
141
-
click *Deploy OVF Template*.
142
-
.. On the *Select an OVF* tab, specify the name of the {op-system} OVA file
143
-
that you downloaded.
144
-
.. On the *Select a name and folder* tab, set a *Virtual machine name*, such
145
-
as {op-system}, click the name of your vSphere cluster, and select the folder you created in the previous step.
146
-
.. On the *Select a compute resource* tab, click the name of your vSphere
147
-
cluster.
71
+
.. From the *Hosts and Clusters* tab, right-click your cluster name and select *Deploy OVF Template*.
72
+
.. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded.
73
+
.. On the *Select a name and folder* tab, set a *Virtual machine name*, such as {op-system}. Click the name of your vSphere cluster and select the folder you created in the previous step.
74
+
.. On the *Select a compute resource* tab, click the name of your vSphere cluster.
148
75
.. On the *Select storage* tab, configure the storage options for your VM.
149
76
*** Select *Thin Provision* or *Thick Provision*, based on your storage preferences.
150
77
*** Select the datastore that you specified in your `install-config.yaml` file.
151
-
.. On the *Select network* tab, specify the network that you configured
152
-
for the cluster, if available.
153
-
.. If you plan to use the same template for all cluster machine types, do not
154
-
specify values on the *Customize template* tab.
78
+
.. On the *Select network* tab, specify the network that you configured for the cluster, if available.
79
+
.. If you plan to use the same template for all cluster machine types, do not specify values on the *Customize template* tab.
155
80
+
156
81
[IMPORTANT]
157
82
====
@@ -160,40 +85,55 @@ installation, do not delete this template.
160
85
====
161
86
162
87
. After the template deploys, deploy a VM for a machine in the cluster.
163
-
.. Right-click the template's name and click *Clone* -> *Clone to Virtual Machine*.
164
-
.. On the *Select a name and folder* tab, specify a name for the VM. You might
165
-
include the machine type in the name, such as `control-plane-0` or `compute-1`.
166
-
.. On the *Select a name and folder* tab, select the name of the folder that
167
-
you created for the cluster.
168
-
.. On the *Select a compute resource* tab, select the name of a host in your
169
-
datacenter.
88
+
.. Right-click the template name and click *Clone* -> *Clone to Virtual Machine*.
89
+
.. On the *Select a name and folder* tab, specify a name for the VM. You might include the machine type in the name, such as `control-plane-0` or `compute-1`.
90
+
.. On the *Select a name and folder* tab, select the name of the folder that you created for the cluster.
91
+
.. On the *Select a compute resource* tab, select the name of a host in your datacenter.
92
+
+
93
+
For a bootstrap machine, specify the URL of the bootstrap Ignition config file that you hosted.
94
+
+
170
95
.. Optional: On the *Select storage* tab, customize the storage options.
171
96
.. On the *Select clone options*, select
172
97
*Customize this virtual machine's hardware*.
173
98
.. On the *Customize hardware* tab, click *VM Options* -> *Advanced*.
99
+
*** Optional: Override default DHCP networking in vSphere. To enable static IP networking:
*** Optional: In the event of cluster performance issues, from the *Latency Sensitivity* list, select *High*.
175
-
*** Click *Edit Configuration*, and on the *Configuration Parameters* window,
176
-
click *Add Configuration Params*. Define the following parameter names and values:
177
-
**** `guestinfo.ignition.config.data`: Paste the contents of the base64-encoded
178
-
Ignition config file for this machine type.
122
+
*** Click *Edit Configuration*, and on the *Configuration Parameters* window, click *Add Configuration Params*. Define the following parameter names and values:
123
+
**** `guestinfo.ignition.config.data`: Paste the contents of the base64-encoded Ignition config file for this machine type.
*** Alternatively, prior to powering on the virtual machine add via vApp properties:
126
+
*** Alternatively, prior to powering on the virtual machine, use vApp properties to:
182
127
**** Navigate to a virtual machine from the vCenter Server inventory.
183
128
**** On the *Configure* tab, expand *Settings* and select *vApp options.*
184
-
**** Scroll down and under *Properties* apply the configurations from above.
185
-
.. In the *Virtual Hardware* panel of the
186
-
*Customize hardware* tab, modify the specified values as required. Ensure that
187
-
the amount of RAM, CPU, and disk storage meets the minimum requirements for the
129
+
**** Scroll down and under *Properties*, apply the configurations that you just edited.
130
+
.. In the *Virtual Hardware* panel of the *Customize hardware* tab, modify the specified values as required. Ensure that the amount of RAM, CPU, and disk storage meets the minimum requirements for the
188
131
machine type.
189
132
.. Complete the configuration and power on the VM.
190
133
191
-
. Create the rest of the machines for your cluster by following the preceding
192
-
steps for each machine.
134
+
. Create the rest of the machines for your cluster by following the preceding steps for each machine.
193
135
+
194
136
[IMPORTANT]
195
137
====
196
-
You must create the bootstrap and control plane machines at this time. Because
197
-
some pods are deployed on compute machines by default, also create at least two
198
-
compute machines before you install the cluster.
138
+
You must create the bootstrap and control plane machines at this time. Because some pods are deployed on compute machines by default, also create at least two compute machines before you install the cluster.
0 commit comments