Skip to content

Commit c939fa6

Browse files
authored
Merge pull request #47341 from jeana-redhat/OSDOCS-3595-gcp-pd-balanced-disks
[OSDOCS-3595]: pd-balanced disks for GCP
2 parents 9ab44c2 + bff4303 commit c939fa6

File tree

2 files changed

+44
-1
lines changed

2 files changed

+44
-1
lines changed

machine_management/creating_machinesets/creating-machineset-gcp.adoc

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,31 @@ toc::[]
88

99
You can create a different machine set to serve a specific purpose in your {product-title} cluster on Google Cloud Platform (GCP). For example, you might create infrastructure machine sets and related machines so that you can move supporting workloads to the new machines.
1010

11+
//[IMPORTANT] admonition for UPI
1112
include::modules/machine-user-provisioned-limitations.adoc[leveloffset=+1]
1213

14+
//Machine API overview
1315
include::modules/machine-api-overview.adoc[leveloffset=+1]
1416

17+
//Sample YAML for a machine set custom resource on GCP
1518
include::modules/machineset-yaml-gcp.adoc[leveloffset=+1]
1619

20+
//Creating a machine set
1721
include::modules/machineset-creating.adoc[leveloffset=+1]
1822

23+
//Configuring persistent disk types by using machine sets
24+
include::modules/machineset-gcp-pd-disk-types.adoc[leveloffset=+1]
25+
26+
//Machine sets that deploy machines as preemptible VM instances
1927
include::modules/machineset-non-guaranteed-instance.adoc[leveloffset=+1]
2028

21-
include::modules/machineset-creating-non-guaranteed-instances.adoc[leveloffset=+1]
29+
//Creating preemptible VM instances by using machine sets
30+
include::modules/machineset-creating-non-guaranteed-instances.adoc[leveloffset=+2]
2231

32+
//Enabling customer-managed encryption keys for a machine set
2333
include::modules/machineset-enabling-customer-managed-encryption.adoc[leveloffset=+1]
34+
//TODO break out procedure as a L2
2435

36+
//Enabling GPU support for a machine set
2537
include::modules/machineset-gcp-enabling-gpu-support.adoc[leveloffset=+1]
38+
//TODO break out procedure as a L2
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * machine_management/creating_machinesets/creating-machineset-gcp.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="machineset-gcp-pd-disk-types_{context}"]
7+
= Configuring persistent disk types by using machine sets
8+
9+
You can configure the type of persistent disk that a machine set deploys machines on by editing the machine set YAML file.
10+
11+
For more information about persistent disk types, compatibility, regional availability, and limitations, see the GCP Compute Engine documentation about link:https://cloud.google.com/compute/docs/disks#pdspecs[persistent disks].
12+
13+
.Procedure
14+
15+
. In a text editor, open the YAML file for an existing machine set or create a new one.
16+
17+
. Edit the following line under the `providerSpec` field:
18+
+
19+
[source,yaml]
20+
----
21+
providerSpec:
22+
value:
23+
disks:
24+
type: <pd-disk-type> <1>
25+
----
26+
<1> Specify the disk persistent type. Valid values are `pd-ssd`, `pd-standard`, and `pd-balanced`. The default value is `pd-standard`.
27+
28+
.Verification
29+
30+
* On the Google Cloud console, review the details for a machine deployed by the machine set and verify that the `Type` field matches the configured disk type.

0 commit comments

Comments
 (0)