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
Applying autoscaling to an {product-title} cluster involves deploying a
9
-
ClusterAutoscaler and then deploying MachineAutoscalers for each Machine type
10
-
in your cluster.
8
+
Applying autoscaling to an {product-title} cluster involves deploying a cluster autoscaler and then deploying machine autoscalers for each Machine type in your cluster.
11
9
12
10
[IMPORTANT]
13
11
====
14
-
You can configure the ClusterAutoscaler only in clusters where the machine API is operational.
12
+
You can configure the cluster autoscaler only in clusters where the machine API is operational.
* After you configure the ClusterAutoscaler, you must configure at least one
41
-
MachineAutoscaler.
36
+
* After you configure the cluster autoscaler, you must configure at least one machine autoscaler.
42
37
43
38
[id="configuring-machineautoscaler"]
44
-
== Configuring the MachineAutoscalers
39
+
== Configuring the machine autoscalers
45
40
46
-
After you deploy the ClusterAutoscaler,
47
-
deploy MachineAutoscaler resources that reference the MachineSets that are used
48
-
to scale the cluster.
41
+
After you deploy the cluster autoscaler, deploy `MachineAutoscaler` resources that reference the machine sets that are used to scale the cluster.
49
42
50
43
[IMPORTANT]
51
44
====
52
-
You must deploy at least one MachineAutoscaler resource after you deploy the
53
-
ClusterAutoscaler resource.
45
+
You must deploy at least one `MachineAutoscaler` resource after you deploy the `ClusterAutoscaler` resource.
54
46
====
55
47
56
48
[NOTE]
57
49
====
58
-
You must configure separate resources for each MachineSet. Remember that
59
-
MachineSets are different in each region, so consider whether you want to
60
-
enable machine scaling in multiple regions. The MachineSet that you scale must have at least one machine in it.
50
+
You must configure separate resources for each machine set. Remember that machine sets are different in each region, so consider whether you want to enable machine scaling in multiple regions. The machine set that you scale must have at least one machine in it.
xref:../nodes/pods/nodes-pods-priority.adoc#nodes-pods-priority[Including pod priority in pod scheduling decisions in {product-title}].
60
+
* For more information about pod priority, see xref:../nodes/pods/nodes-pods-priority.adoc#nodes-pods-priority[Including pod priority in pod scheduling decisions in {product-title}].
Copy file name to clipboardExpand all lines: machine_management/creating-infrastructure-machinesets.adoc
+13-35Lines changed: 13 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,60 +1,40 @@
1
1
[id="creating-infrastructure-machinesets"]
2
-
= Creating infrastructure MachineSets
2
+
= Creating infrastructure machine sets
3
3
include::modules/common-attributes.adoc[]
4
4
:context: creating-infrastructure-machinesets
5
5
6
6
toc::[]
7
7
8
-
You can create a MachineSet to host only infrastructure components.
9
-
You apply specific Kubernetes labels to these Machines and then
10
-
update the infrastructure components to run on only those Machines. These
11
-
infrastructure nodes are not counted toward the total number of subscriptions
12
-
that are required to run the environment.
8
+
You can create a machine set to host only infrastructure components. You apply specific Kubernetes labels to these machines and then update the infrastructure components to run on only those machines. These infrastructure nodes are not counted toward the total number of subscriptions that are required to run the environment.
13
9
14
10
[IMPORTANT]
15
11
====
16
-
Unlike earlier versions of {product-title}, you cannot move the infrastructure
17
-
components to the master Machines. To move the components, you must create a
18
-
new MachineSet.
12
+
Unlike earlier versions of {product-title}, you cannot move the infrastructure components to the master machines. To move the components, you must create a new machine set.
== Creating infrastructure MachineSets for production environments
18
+
== Creating infrastructure machine sets for production environments
25
19
26
-
In a production deployment, deploy at least three MachineSets to hold
27
-
infrastructure components. Both the logging aggregation solution and
28
-
the service mesh deploy Elasticsearch, and Elasticsearch requires three
29
-
instances that are installed on different nodes. For high availability, install
30
-
deploy these nodes to different availability zones. Since you need different
31
-
MachineSets for each availability zone, create at least three MachineSets.
20
+
In a production deployment, deploy at least three machine sets to hold infrastructure components. Both the logging aggregation solution and the service mesh deploy Elasticsearch, and Elasticsearch requires three instances that are installed on different nodes. For high availability, deploy these nodes to different availability zones. Since you need different machine sets for each availability zone, create at least three machine sets.
MachineSets running on AWS support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#machineset-non-guaranteed-instance_creating-machineset-aws[Spot Instances].
41
-
You can save on costs by using Spot Instances at a lower price compared to
42
-
On-Demand Instances on AWS. xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-aws[Configure Spot Instances]
43
-
by adding `spotMarketOptions` to the MachineSet YAML file.
29
+
Machine sets running on AWS support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#machineset-non-guaranteed-instance_creating-machineset-aws[Spot Instances]. You can save on costs by using Spot Instances at a lower price compared to On-Demand Instances on AWS. xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-aws[Configure Spot Instances] by adding `spotMarketOptions` to the machine set YAML file.
MachineSets running on Azure support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-azure.adoc#machineset-non-guaranteed-instance_creating-machineset-azure[Spot VMs].
48
-
You can save on costs by using Spot VMs at a lower price compared to
49
-
standard VMs on Azure. You can xref:../machine_management/creating_machinesets/creating-machineset-azure.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-azure[configure Spot VMs]
50
-
by adding `spotVMOptions` to the MachineSet YAML file.
33
+
Machine sets running on Azure support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-azure.adoc#machineset-non-guaranteed-instance_creating-machineset-azure[Spot VMs]. You can save on costs by using Spot VMs at a lower price compared to standard VMs on Azure. You can xref:../machine_management/creating_machinesets/creating-machineset-azure.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-azure[configure Spot VMs] by adding `spotVMOptions` to the machine set YAML file.
MachineSets running on GCP support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-non-guaranteed-instance_creating-machineset-gcp[preemptible VM instances].
55
-
You can save on costs by using preemptible VM instances at a lower price
56
-
compared to normal instances on GCP. You can xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-gcp[configure preemptible VM instances]
57
-
by adding `preemptible` to the MachineSet YAML file.
37
+
Machine sets running on GCP support non-guaranteed xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-non-guaranteed-instance_creating-machineset-gcp[preemptible VM instances]. You can save on costs by using preemptible VM instances at a lower price compared to normal instances on GCP. You can xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-gcp[configure preemptible VM instances] by adding `preemptible` to the machine set YAML file.
* See xref:../nodes/scheduling/nodes-scheduler-about.adoc#nodes-scheduler-about[Controlling pod placement using the scheduler] for general information on scheduling a pod to a node.
77
-
* See xref:moving-resources-to-infrastructure-machinesets[Moving resources to infrastructure machine sets]
78
-
for instructions on scheduling pods to infra nodes.
57
+
* See xref:moving-resources-to-infrastructure-machinesets[Moving resources to infrastructure machine sets] for instructions on scheduling pods to infra nodes.
Copy file name to clipboardExpand all lines: machine_management/creating_machinesets/creating-machineset-aws.adoc
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,9 @@
1
1
[id="creating-machineset-aws"]
2
-
= Creating a MachineSet in AWS
2
+
= Creating a machine set in AWS
3
3
include::modules/common-attributes.adoc[]
4
4
:context: creating-machineset-aws
5
5
6
-
You can create a different MachineSet to serve a specific purpose in your
7
-
{product-title} cluster on Amazon Web Services (AWS). For example, you might
8
-
create infrastructure MachineSets and related Machines so that you can move
9
-
supporting workloads to the new Machines.
6
+
You can create a different machine set to serve a specific purpose in your {product-title} cluster on Amazon Web Services (AWS). For example, you might create infrastructure machine sets and related machines so that you can move supporting workloads to the new machines.
Copy file name to clipboardExpand all lines: machine_management/creating_machinesets/creating-machineset-azure.adoc
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,9 @@
1
1
[id="creating-machineset-azure"]
2
-
= Creating a MachineSet in Azure
2
+
= Creating a machine set in Azure
3
3
include::modules/common-attributes.adoc[]
4
4
:context: creating-machineset-azure
5
5
6
-
You can create a different MachineSet to serve a specific purpose in your
7
-
{product-title} cluster on Microsoft Azure. For example, you might
8
-
create infrastructure MachineSets and related Machines so that you can move
9
-
supporting workloads to the new Machines.
6
+
You can create a different machine set to serve a specific purpose in your {product-title} cluster on Microsoft Azure. For example, you might create infrastructure machine sets and related Machines so that you can move supporting workloads to the new Machines.
Copy file name to clipboardExpand all lines: machine_management/creating_machinesets/creating-machineset-vsphere.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
[id="creating-machineset-vsphere"]
2
-
= Creating a MachineSet on vSphere
2
+
= Creating a machine set on vSphere
3
3
include::modules/common-attributes.adoc[]
4
4
:context: creating-machineset-vsphere
5
5
6
6
toc::[]
7
7
8
-
You can create a different MachineSet to serve a specific purpose in your {product-title} cluster on VMware vSphere. For example, you might create infrastructure MachineSets and related Machines so that you can move supporting workloads to the new Machines.
8
+
You can create a different machine set to serve a specific purpose in your {product-title} cluster on VMware vSphere. For example, you might create infrastructure machine sets and related Machines so that you can move supporting workloads to the new Machines.
You can add or remove an instance of a machine in a MachineSet.
8
+
You can add or remove an instance of a machine in a machine set.
9
9
10
10
[NOTE]
11
11
====
12
-
If you need to modify aspects of a MachineSet outside of scaling,
13
-
see xref:../machine_management/modifying-machineset.adoc#modifying-machineset[Modifying a MachineSet].
12
+
If you need to modify aspects of a machine set outside of scaling, see xref:../machine_management/modifying-machineset.adoc#modifying-machineset[Modifying a machine set].
Copy file name to clipboardExpand all lines: machine_management/modifying-machineset.adoc
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,16 @@
1
1
[id="modifying-machineset"]
2
-
= Modifying a MachineSet
2
+
= Modifying a machine set
3
3
include::modules/common-attributes.adoc[]
4
4
:context: modifying-machineset
5
5
6
6
toc::[]
7
7
8
8
9
-
You can make changes to a MachineSet, such as adding labels, changing the instance type,
10
-
or changing block storage.
9
+
You can make changes to a machine set, such as adding labels, changing the instance type, or changing block storage.
11
10
12
11
[NOTE]
13
12
====
14
-
If you need to scale a MachineSet without making other changes,
15
-
see xref:../machine_management/manually-scaling-machineset.adoc#manually-scaling-machineset[Manually scaling a MachineSet].
13
+
If you need to scale a machine set without making other changes, see xref:../machine_management/manually-scaling-machineset.adoc#manually-scaling-machineset[Manually scaling a machine set].
0 commit comments