openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #105710 from openshift-cherrypick-robot/cherry-pick-105709-to-enterprise-4.21

Browse Source 
[enterprise-4.21] patch snippets out of conditional blocks for build
This commit is contained in:
Kathryn Alexander
2026-01-29 15:23:54 -05:00
committed by GitHub
parent e19ce1fc45 a5ed7d5629
commit 107e7b3fbe
3 changed files with 12 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
modules/machineset-creating-non-guaranteed-instances.adoc
View File

@@ -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

10
modules/machineset-non-guaranteed-instance.adoc
View File

@@ -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.

11
snippets/google-spot-over-preemtible.adoc
View File

@@ -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.
====