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 can add or remove an instance of a machine in a compute machine set.
10
10
11
-
[NOTE]
12
-
====
13
-
If you need to modify aspects of a compute machine set outside of scaling, see xref:../../../machine_management/compute_machine_management/mapi_compute_managing_machines/modifying-machineset.adoc#modifying-machineset[Modifying a compute machine set].
14
-
====
11
+
// [NOTE]
12
+
// ====
13
+
// If you need to modify aspects of a compute machine set outside of scaling, see xref:../../../machine_management/compute_machine_management/mapi_compute_managing_machines/modifying-machineset.adoc#modifying-machineset[Modifying a compute machine set].
14
+
// ====
15
15
16
16
== Prerequisites
17
17
18
18
* If you enabled the cluster-wide proxy and scale up compute machines not included in `networking.machineNetwork[].cidr` from the installation configuration, you must xref:../../../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[add the compute machines to the Proxy object's `noProxy` field] to prevent connection issues.
* xref:../../../machine_management/manual_machine_management/deleting-machine.adoc#machine-lifecycle-hook-deletion_deleting-machine[Lifecycle hooks for the machine deletion phase]
29
+
// * xref:../../../machine_management/manual_machine_management/deleting-machine.adoc#machine-lifecycle-hook-deletion_deleting-machine[Lifecycle hooks for the machine deletion phase]
You can modify a compute machine set, such as adding labels, changing the instance type, or changing block storage.
10
+
11
+
// [NOTE]
12
+
// ====
13
+
// If you need to scale a compute machine set without making other changes, see xref:../../../machine_management/compute_machine_management/mapi_compute_managing_machines/manually-scaling-machineset.adoc#manually-scaling-machineset[Manually scaling a compute machine set].
// * xref:../../../machine_management/manual_machine_management/deleting-machine.adoc#machine-lifecycle-hook-deletion_deleting-machine[Lifecycle hooks for the machine deletion phase]
23
+
// * xref:../../../machine_management/compute_machine_management/mapi_compute_managing_machines/manually-scaling-machineset.adoc#machineset-manually-scaling_manually-scaling-machineset[Scaling a compute machine set manually]
24
+
// * xref:../../../nodes/scheduling/nodes-scheduler-about.adoc#nodes-scheduler-about[Controlling pod placement using the scheduler]
* xref:../../machine_management/cluster_api_machine_management/cluster_api_provider_configurations/cluster-api-config-options-azure.adoc#capi-yaml-machine-template-azure_cluster-api-config-options-azure[Sample YAML for a Cluster API machine template resource on {azure-full}]
19
19
* xref:../../machine_management/cluster_api_machine_management/cluster_api_provider_configurations/cluster-api-config-options-rhosp.adoc#capi-yaml-machine-template-rhosp_cluster-api-config-options-rhosp[Sample YAML for a Cluster API machine template resource on {rh-openstack}]
20
20
* xref:../../machine_management/cluster_api_machine_management/cluster_api_provider_configurations/cluster-api-config-options-vsphere.adoc#capi-yaml-machine-template-vsphere_cluster-api-config-options-vsphere[Sample YAML for a Cluster API machine template resource on {vmw-full}]
21
-
* xref:../../machine_management/cluster_api_machine_management/cluster-api-managing-machines.adoc#machineset-modifying_cluster-api-managing-machines[Modifying a compute machine set by using the CLI]
* xref:../../machine_management/cluster_api_machine_management/cluster_api_provider_configurations/cluster-api-config-options-aws.adoc#capi-yaml-machine-set-aws_cluster-api-config-options-aws[Sample YAML for a Cluster API compute machine set resource on {aws-full}]
* xref:../../machine_management/manual_machine_management/deleting-machine.adoc#machine-lifecycle-hook-deletion_deleting-machine[Lifecycle hooks for the machine deletion phase]
Copy file name to clipboardExpand all lines: machine_management/index.adoc
+2-2
Original file line number
Diff line number
Diff line change
@@ -55,9 +55,9 @@ As a cluster administrator, you can perform the following actions:
55
55
56
56
* Create a machine set for a bare metal deployment: xref:../machine_management/creating_machinesets/creating-machineset-bare-metal.adoc#creating-machineset-bare-metal[Creating a compute machine set on bare metal]
57
57
58
-
* xref:../machine_management/compute_machine_management/mapi_compute_managing_machines/manually-scaling-machineset.adoc#manually-scaling-machineset[Manually scale a compute machine set] by adding or removing a machine from the compute machine set.
58
+
* xref:../machine_management/compute_machine_management/mapi-compute-managing-machines.adoc#mapi-compute-scaling_mapi-compute-managing-machines[Manually scale a compute machine set] by adding or removing a machine from the compute machine set.
59
59
60
-
* xref:../machine_management/compute_machine_management/mapi_compute_managing_machines/modifying-machineset.adoc#modifying-machineset[Modify a compute machine set] through the `MachineSet` YAML configuration file.
60
+
* xref:../machine_management/compute_machine_management/mapi-compute-managing-machines.adoc#mapi-compute-config-updating-cli_mapi-compute-managing-machines[Updating compute machine configurations] through the `MachineSet` YAML configuration file.
61
61
62
62
* xref:../machine_management/manual_machine_management/deleting-machine.adoc#deleting-machine[Delete] a machine.
* For any Cluster API compute machine sets that reference this template, update the `spec.template.spec.infrastructureRef.name` parameter to match the `metadata.name` value in the new machine template resource.
94
-
For more information, see "Modifying a compute machine set by using the CLI."
94
+
For more information, see "Updating compute machine configurations."
Copy file name to clipboardExpand all lines: modules/machineset-delete-policy.adoc
+2
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@
6
6
[id="machineset-delete-policy_{context}"]
7
7
= The compute machine set deletion policy
8
8
9
+
//needs a rewrite
10
+
9
11
`Random`, `Newest`, and `Oldest` are the three supported deletion options. The default is `Random`, meaning that random machines are chosen and deleted when scaling compute machine sets down. The deletion policy can be set according to the use case by modifying the particular compute machine set:
To add or remove an instance of a machine in a compute machine set, you can manually scale the compute machine set.
12
13
13
-
This guidance is relevant to fully automated, installer-provisioned infrastructure installations. Customized, user-provisioned infrastructure installations do not have compute machine sets.
* Install an {product-title} cluster and the `oc` command line.
20
+
* Install an {product-title} cluster and the {oc-first}.
18
21
* Log in to `oc` as a user with `cluster-admin` permission.
22
+
* If have you enabled the cluster-wide proxy, you must add any compute machines that are not included in the `networking.machineNetwork[].cidr` field in the installation configuration file to the `noProxy` field in the `Proxy` object before scaling them up to prevent connection issues.
23
+
For more information, see "Enabling the cluster-wide proxy".
19
24
20
25
.Procedure
21
26
22
-
. View the compute machine sets that are in the cluster by running the following command:
27
+
. List the compute machine sets that are in the cluster by running the following command:
23
28
+
24
29
[source,terminal]
25
30
----
26
31
$ oc get machinesets.machine.openshift.io -n openshift-machine-api
27
32
----
28
33
+
29
-
The compute machine sets are listed in the form of `<clusterid>-worker-<aws-region-az>`.
34
+
The compute machine sets are listed in the form of `<cluster_id>-worker-<region>`.
30
35
31
-
. View the compute machines that are in the cluster by running the following command:
36
+
. List the compute machines that are in the cluster by running the following command:
32
37
+
33
38
[source,terminal]
34
39
----
@@ -39,21 +44,24 @@ $ oc get machines.machine.openshift.io -n openshift-machine-api
Copy file name to clipboardExpand all lines: post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.adoc
0 commit comments