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
Copy file name to clipboardExpand all lines: README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ This Terraform module deploys various resources to run Atlantis on Google Comput
43
43
44
44
-**Separate Persistent Data Disk** - The VM instance has a separate attached persistent data disk attached to it to ensure that Atlantis data is persisted and not lost if the VM is deleted or terminated.
45
45
46
-
-**Hyperdisk auto-detection** - Hyperdisk-only machine families (C4A, C4D, H4D, X4, M4, A4X, A4, A3 Ultra, A3 Mega) are detected automatically so both boot and persistent disks default to Hyperdisk-balanced while still allowing explicit Hyperdisk overrides.
46
+
-**Hyperdisk auto-detection** - Hyperdisk-only machine families (C4D, H4D, X4, M4, A3 Ultra, A3 Mega) are detected automatically so both boot and persistent disks default to Hyperdisk-balanced while still allowing explicit Hyperdisk overrides.
47
47
48
48
-**Shielded VM** - A Shielded VM is a VM that's hardened by a set of security controls that help defend against rootkits and bootkits. Using a Shielded VM helps protect enterprise workloads from threats like remote attacks, privilege escalation, and malicious insiders.
49
49
@@ -53,11 +53,11 @@ This Terraform module deploys various resources to run Atlantis on Google Comput
53
53
54
54
## Hyperdisk Support
55
55
56
-
Hyperdisk storage is required for the following machine series: **C4A, C4D, H4D, X4, M4, A4X, A4, A3 Ultra, and A3 Mega**. The module automatically detects these machine types and switches both the boot disk and persistent data disk to `hyperdisk-balanced` when no override is provided, so Hyperdisk-only workloads work out of the box.
56
+
Hyperdisk storage is required for the following machine series: **C4D, H4D, X4, M4, A3 Ultra, and A3 Mega**. The module automatically detects these machine types and switches both the boot disk and persistent data disk to `hyperdisk-balanced` when no override is provided, so Hyperdisk-only workloads work out of the box.
57
57
58
58
To force a different Hyperdisk flavor you can set `persistent_disk_type` or the new `boot_disk_type` variable to values such as `hyperdisk-extreme`. The `persistent_disk_type` validation prevents `pd-*` disks from being combined with the Hyperdisk-only families, which helps catch mistakes early.
59
59
60
-
See [`examples/c4a-machine`](examples/c4a-machine) for a complete configuration using the `c4a-standard-4` machine type along with guidance on optional overrides.
60
+
**Note:** ARM64 machine types (C4A, A4X, A4, T2A, T2D) are **not supported** because Atlantis does not run on ARM64 architecture. Please use x86-64 machine types instead.
61
61
62
62
## Prerequisites
63
63
@@ -77,7 +77,6 @@ Here are some examples to choose from. Look at the prerequisites above to find o
Google currently requires Hyperdisk storage for C4A, C4D, H4D, X4, M4, A4X, A4, A3 Ultra, and A3 Mega machine types. This module detects those families automatically so the boot and persistent disks default to `hyperdisk-balanced`. You can still set `persistent_disk_type` or `boot_disk_type` to another Hyperdisk flavor (for example `hyperdisk-extreme`) when you need higher throughput.
183
+
Google currently requires Hyperdisk storage for C4D, H4D, X4, M4, A3 Ultra, and A3 Mega machine types. This module detects those families automatically so the boot and persistent disks default to `hyperdisk-balanced`. You can still set `persistent_disk_type` or `boot_disk_type` to another Hyperdisk flavor (for example `hyperdisk-extreme`) when you need higher throughput.
184
+
185
+
**Note:** ARM64 machine types (C4A, A4X, A4, T2A, T2D) are not supported.
185
186
186
187
### When sending an HTTP request, I'm receiving an ERR_EMPTY_RESPONSE error
@@ -36,10 +36,13 @@ The `persistent_disk_type` variable prevents pairing Hyperdisk-only machine type
36
36
37
37
```sh
38
38
# Should fail: pd-ssd on a Hyperdisk machine
39
-
terraform plan -var 'machine_type=c4a-standard-4' -var 'persistent_disk_type=pd-ssd'
39
+
terraform plan -var 'machine_type=c4d-standard-4' -var 'persistent_disk_type=pd-ssd'
40
40
41
41
# Should pass: Hyperdisk override
42
-
terraform plan -var 'machine_type=c4a-standard-4' -var 'persistent_disk_type=hyperdisk-extreme'
42
+
terraform plan -var 'machine_type=c4d-standard-4' -var 'persistent_disk_type=hyperdisk-extreme'
43
+
44
+
# Should fail: ARM64 machine type
45
+
terraform plan -var 'machine_type=c4a-standard-4'
43
46
```
44
47
45
48
Running these steps after any related change ensures the Hyperdisk detection, overrides, and validation logic continue working until a formal automated suite is added.
Copy file name to clipboardExpand all lines: variables.tf
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,13 @@ variable "machine_type" {
33
33
type=string
34
34
description="The machine type to run Atlantis on. Hyperdisk-only families (C4A, C4D, H4D, X4, M4, A4X, A4, A3 Ultra, A3 Mega) require Hyperdisk storage and will trigger automatic Hyperdisk disk selection."
error_message="ARM64 machine types (C4A, A4X, A4, T2A, T2D) are not supported because Atlantis does not run on ARM64 architecture. Please use an x86-64 machine type instead."
0 commit comments