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
* xref:../../post_installation_configuration/machine-configuration-tasks.adoc#understanding-the-machine-config-operator[Understanding the Machine Config Operator]
36
+
* xref:../../installing/installing_vsphere/installing-vsphere.adoc#installation-vsphere-machines_installing-vsphere[Installing {op-system} and starting the {product-title} bootstrap process]
Copy file name to clipboardExpand all lines: machine_management/user_infra/adding-compute-user-infra-general.adoc
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
:_content-type: ASSEMBLY
2
2
[id="adding-compute-user-infra-general"]
3
-
= Adding compute machines to clusters with user-provisioned infrastructure
3
+
= Adding compute machines to clusters with user-provisioned infrastructure manually
4
4
include::_attributes/common-attributes.adoc[]
5
5
:context: adding-compute-user-infra-general
6
6
@@ -31,7 +31,9 @@ To add more compute machines to your {product-title} cluster on Google Cloud Pla
31
31
[id="upi-adding-compute-vsphere"]
32
32
== Adding compute machines to vSphere
33
33
34
-
To add more compute machines to your {product-title} cluster on vSphere, see xref:../../machine_management/user_infra/adding-vsphere-compute-user-infra.adoc#adding-vsphere-compute-user-infra[Adding compute machines to vSphere].
34
+
You can xref:../../machine_management/creating_machinesets/creating-machineset-vsphere.adoc#creating-machineset-vsphere[use compute machine sets] to automate the creation of additional compute machines for your {product-title} cluster on vSphere.
35
+
36
+
To manually add more compute machines to your cluster, see xref:../../machine_management/user_infra/adding-vsphere-compute-user-infra.adoc#adding-vsphere-compute-user-infra[Adding compute machines to vSphere manually].
Copy file name to clipboardExpand all lines: machine_management/user_infra/adding-vsphere-compute-user-infra.adoc
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,17 @@
1
1
:_content-type: ASSEMBLY
2
2
[id="adding-vsphere-compute-user-infra"]
3
-
= Adding compute machines to vSphere
3
+
= Adding compute machines to vSphere manually
4
4
include::_attributes/common-attributes.adoc[]
5
5
:context: adding-vsphere-compute-user-infra
6
6
7
7
toc::[]
8
8
9
-
You can add more compute machines to your {product-title} cluster on VMware vSphere.
9
+
You can add more compute machines to your {product-title} cluster on VMware vSphere manually.
10
+
11
+
[NOTE]
12
+
====
13
+
You can also xref:../../machine_management/creating_machinesets/creating-machineset-vsphere.adoc#creating-machineset-vsphere[use compute machine sets] to automate the creation of additional VMware vSphere compute machines for your cluster.
= Requirements for clusters with user-provisioned infrastructure to use compute machine sets
14
+
15
+
To use compute machine sets on clusters that have user-provisioned infrastructure, you must ensure that you cluster configuration supports using the Machine API.
Clusters that are installed with the platform type `none` are unable to use some features, such as managing compute machines with the Machine API. This limitation applies even if the compute machines that are attached to the cluster are installed on a platform that would normally support the feature. This parameter cannot be changed after installation.
259
+
====
255
260
ifndef::openshift-origin[]
256
261
<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/machine-user-provisioned-limitations.adoc
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,5 +15,14 @@
15
15
16
16
[IMPORTANT]
17
17
====
18
-
This process is not applicable for clusters with manually provisioned machines. You can use the advanced machine management and scaling capabilities only in clusters where the Machine API is operational.
18
+
You can use the advanced machine management and scaling capabilities only in clusters where the Machine API is operational. Clusters with user-provisioned infrastructure require additional validation and configuration to use the Machine API.
19
+
20
+
Clusters with the infrastructure platform type `none` cannot use the Machine API. This limitation applies even if the compute machines that are attached to the cluster are installed on a platform that supports the feature. This parameter cannot be changed after installation.
21
+
22
+
To view the platform type for your cluster, run the following command:
23
+
24
+
[source,terminal]
25
+
----
26
+
$ oc get infrastructure cluster -o jsonpath='{.status.platform}'
Copy file name to clipboardExpand all lines: modules/machineset-creating.adoc
+96-92Lines changed: 96 additions & 92 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,16 +33,23 @@ endif::[]
33
33
[id="machineset-creating_{context}"]
34
34
= Creating a compute machine set
35
35
36
-
In addition to the ones created by the installation program, you can create your own compute machine sets to dynamically manage the machine compute resources for specific workloads of your choice.
36
+
In addition to the compute machine sets created by the installation program, you can create your own to dynamically manage the machine compute resources for specific workloads of your choice.
37
+
38
+
ifdef::vsphere[]
39
+
[NOTE]
40
+
====
41
+
Clusters that are installed with user-provisioned infrastructure have a different networking stack than clusters with infrastructure that is provisioned by the installation program. As a result of this difference, automatic load balancer management is unsupported on clusters that have user-provisioned infrastructure. For these clusters, a compute machine set can only create `worker` and `infra` type machines.
42
+
====
43
+
endif::vsphere[]
37
44
38
45
.Prerequisites
39
46
40
47
* Deploy an {product-title} cluster.
41
48
* Install the OpenShift CLI (`oc`).
42
49
* Log in to `oc` as a user with `cluster-admin` permission.
43
50
ifdef::vsphere[]
44
-
* Create a tag inside your vCenter instance based on the cluster API name. This tag is utilized by the compute machine set to associate the {product-title} nodes to the provisioned virtual machines (VM). For directions on creating tags in vCenter, see the VMware documentation for link:https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-E8E854DD-AA97-4E0C-8419-CE84F93C4058.html[vSphere Tags and Attributes].
45
51
* Have the necessary permissions to deploy VMs in your vCenter instance and have the required access to the datastore specified.
52
+
* If your cluster uses user-provisioned infrastructure, you have satisfied the specific Machine API requirements for that configuration.
46
53
endif::vsphere[]
47
54
ifdef::ash[]
48
55
* Create an availability set in which to deploy Azure Stack Hub compute machines.
@@ -59,7 +66,9 @@ ifdef::ash[]
59
66
Ensure that you set the `<availabilitySet>`, `<clusterID>`, and `<role>` parameter values.
60
67
endif::ash[]
61
68
62
-
.. If you are not sure which value to set for a specific field, you can check an existing compute machine set from your cluster:
69
+
. Optional: If you are not sure which value to set for a specific field, you can check an existing compute machine set from your cluster.
70
+
71
+
.. To list the compute machine sets in your cluster, run the following command:
For clusters that have user-provisioned infrastructure, a compute machine set can only create `worker` and `infra` type machines.
132
+
====
133
+
<3> The values in the `<providerSpec>` section of the compute machine set CR are platform-specific. For more information about `<providerSpec>` parameters in the CR, see the sample compute machine set CR configuration for your provider.
134
+
--
103
135
104
-
. Create the new `MachineSet` CR:
136
+
ifdef::vsphere[]
137
+
.. If you are creating a compute machine set for a cluster that has user-provisioned infrastructure, note the following important values:
138
+
+
139
+
.Example vSphere `providerSpec` values
140
+
[source,yaml]
141
+
----
142
+
apiVersion: machine.openshift.io/v1beta1
143
+
kind: MachineSet
144
+
...
145
+
template:
146
+
...
147
+
spec:
148
+
providerSpec:
149
+
value:
150
+
apiVersion: machine.openshift.io/v1beta1
151
+
credentialsSecret:
152
+
name: vsphere-cloud-credentials <1>
153
+
diskGiB: 120
154
+
kind: VSphereMachineProviderSpec
155
+
memoryMiB: 16384
156
+
network:
157
+
devices:
158
+
- networkName: "<vm_network_name>"
159
+
numCPUs: 4
160
+
numCoresPerSocket: 4
161
+
snapshot: ""
162
+
template: <vm_template_name> <2>
163
+
userDataSecret:
164
+
name: worker-user-data <3>
165
+
workspace:
166
+
datacenter: <vcenter_datacenter_name>
167
+
datastore: <vcenter_datastore_name>
168
+
folder: <vcenter_vm_folder_path>
169
+
resourcepool: <vsphere_resource_pool>
170
+
server: <vcenter_server_address> <4>
171
+
----
172
+
<1> The name of the secret in the `openshift-machine-api` namespace that contains the required vCenter credentials.
173
+
<2> The name of the {op-system} VM template for your cluster that was created during installation.
174
+
<3> The name of the secret in the `openshift-machine-api` namespace that contains the required Ignition configuration credentials.
175
+
<4> The IP address or fully qualified domain name (FQDN) of the vCenter server.
176
+
endif::vsphere[]
177
+
178
+
. Create a `MachineSet` CR by running the following command:
. If you need compute machine sets in other availability zones, repeat this process to create more compute machine sets.
187
+
endif::[]
188
+
189
+
.Verification
190
+
191
+
* View the list of compute machine sets by running the following command:
112
192
+
113
193
[source,terminal]
114
194
----
@@ -142,82 +222,6 @@ endif::win[]
142
222
+
143
223
When the new compute machine set is available, the `DESIRED` and `CURRENT` values match. If the compute machine set is not available, wait a few minutes and run the command again.
144
224
145
-
////
146
-
This step is not needed. No machines at this point.
147
-
148
-
. After the new compute machine set is available, check status of the machine and the node that it references:
This step is not needed. I have not labeled a node yet.
200
-
201
-
. View the node you want to assign as the infra node to confirm that the node has the label that you specified:
202
-
+
203
-
[source,terminal]
204
-
----
205
-
$ oc get node <node_name> --show-labels
206
-
----
207
-
+
208
-
Review the command output and confirm that `node-role.kubernetes.io/<your_label>` is in the `LABELS` list.
209
-
210
-
[NOTE]
211
-
====
212
-
Any change to a compute machine set is not applied to existing machines owned by the compute machine set. For example, labels edited or added to an existing compute machine set are not propagated to existing machines and nodes associated with the compute machine set.
0 commit comments