From a5ed7d5629c85626f601915376ac7be44f6d1981 Mon Sep 17 00:00:00 2001 From: Jeana Routh Date: Thu, 29 Jan 2026 14:59:31 -0500 Subject: [PATCH] patch snippets out of conditional blocks for build --- .../machineset-creating-non-guaranteed-instances.adoc | 5 ++++- modules/machineset-non-guaranteed-instance.adoc | 10 ++++++++-- snippets/google-spot-over-preemtible.adoc | 11 ----------- 3 files changed, 12 insertions(+), 14 deletions(-) delete mode 100644 snippets/google-spot-over-preemtible.adoc diff --git a/modules/machineset-creating-non-guaranteed-instances.adoc b/modules/machineset-creating-non-guaranteed-instances.adoc index f3404923ef..f5d593228a 100644 --- a/modules/machineset-creating-non-guaranteed-instances.adoc +++ b/modules/machineset-creating-non-guaranteed-instances.adoc @@ -32,7 +32,10 @@ ifdef::gcp[To launch a Spot VM on {gcp-short}, you add `provisioningModel: "Spot ifdef::gcp-legacy-preempt[] To launch a preemptible VM instance on {gcp-short}, you add `preemptible` to your compute machine set YAML file. -include::snippets/google-spot-over-preemtible.adoc[] +[NOTE] +==== +{gcp-short} recommends using Spot VMs over preemptible VMs because Spot VMs include new features that preemptible VMs do not support. +==== endif::[] .Procedure diff --git a/modules/machineset-non-guaranteed-instance.adoc b/modules/machineset-non-guaranteed-instance.adoc index 5fd7fddd24..1612df5523 100644 --- a/modules/machineset-non-guaranteed-instance.adoc +++ b/modules/machineset-non-guaranteed-instance.adoc @@ -66,7 +66,10 @@ Interruptions can occur when using Spot VMs for the following reasons: When Azure terminates an instance, a termination handler running on the Spot VM node deletes the machine resource. To satisfy the compute machine set `replicas` quantity, the compute machine set creates a machine that requests a Spot VM. endif::azure[] ifdef::gcp[] -include::snippets/google-spot-over-preemtible.adoc[] +[NOTE] +==== +{gcp-short} recommends using Spot VMs over preemptible VMs because Spot VMs include new features that preemptible VMs do not support. +==== {gcp-short} Compute Engine can terminate a Spot VM at any time. Compute Engine sends a best-effort preemption notice to the user indicating that an interruption will occur after 30 seconds. @@ -83,7 +86,10 @@ When {gcp-short} terminates an instance, a termination handler running on the Sp To satisfy the compute machine set `replicas` quantity, the compute machine set creates a machine that requests a Spot VM. endif::gcp[] ifdef::gcp-legacy-preempt[] -include::snippets/google-spot-over-preemtible.adoc[] +[NOTE] +==== +{gcp-short} recommends using Spot VMs over preemptible VMs because Spot VMs include new features that preemptible VMs do not support. +==== {gcp-short} Compute Engine can terminate a preemptible VM instance at any time. Compute Engine sends a preemption notice to the user indicating that an interruption will occur after 30 seconds. {product-title} begins to remove the workloads from the affected instances when Compute Engine issues the preemption notice. An ACPI G3 Mechanical Off signal is sent to the operating system after 30 seconds if the instance is not stopped. The preemptible VM instance is then transitioned to a `TERMINATED` state by Compute Engine. diff --git a/snippets/google-spot-over-preemtible.adoc b/snippets/google-spot-over-preemtible.adoc deleted file mode 100644 index 18d55d6a6a..0000000000 --- a/snippets/google-spot-over-preemtible.adoc +++ /dev/null @@ -1,11 +0,0 @@ -// Text snippet included in the following modules: -// -// * modules/machineset-creating-non-guaranteed-instances.adoc -// * modules/machineset-non-guaranteed-instance.adoc - -:_mod-docs-content-type: SNIPPET - -[NOTE] -==== -{gcp-short} recommends using Spot VMs over preemptible VMs because Spot VMs include new features that preemptible VMs do not support. -==== \ No newline at end of file