Skip to content

chore(NA): use different gcp zones for spot instances#248181

Merged
mistic merged 84 commits intoelastic:mainfrom
mistic:default-override-spot-zones
Jan 29, 2026
Merged

chore(NA): use different gcp zones for spot instances#248181
mistic merged 84 commits intoelastic:mainfrom
mistic:default-override-spot-zones

Conversation

@mistic
Copy link
Copy Markdown
Contributor

@mistic mistic commented Jan 7, 2026

Closes https://github.com/elastic/kibana-operations/issues/414

This PR declares spotZones to be used on preemptible machine based jobs according to data we have of zones that historically have been failing the most over the past couple months.

@mistic mistic added chore Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting v9.4.0 labels Jan 7, 2026
@elastic elastic deleted a comment from elasticmachine Jan 8, 2026
@mistic mistic self-assigned this Jan 8, 2026
@mistic mistic force-pushed the default-override-spot-zones branch 2 times, most recently from a6c2a8b to 8109230 Compare January 9, 2026 02:38
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

cc @mistic

@mistic mistic added backport:all-open Backport to all branches that could still receive a release and removed backport:skip This PR does not require backporting labels Jan 29, 2026
@mistic mistic merged commit 7c88eee into elastic:main Jan 29, 2026
20 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 8.19, 9.1, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/21484688420

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts
9.1 Backport failed because of merge conflicts
9.2 Backport failed because of merge conflicts
9.3 An unhandled error occurred. Please see the logs for details

Manual backport

To create the backport manually run:

node scripts/backport --pr 248181

Questions ?

Please refer to the Backport tool documentation

hannahbrooks pushed a commit to hannahbrooks/kibana that referenced this pull request Jan 30, 2026
Closes elastic/kibana-operations#414

This PR declares spotZones to be used on preemptible machine based jobs
according to data we have of zones that historically have been failing
the most over the past couple months.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
mistic added a commit to mistic/kibana that referenced this pull request Jan 31, 2026
Closes elastic/kibana-operations#414

This PR declares spotZones to be used on preemptible machine based jobs
according to data we have of zones that historically have been failing
the most over the past couple months.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
(cherry picked from commit 7c88eee)

# Conflicts:
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/scout_uiam_tests.yml
#	.buildkite/pipelines/pull_request/security_solution/ai4dsoc.yml
#	.buildkite/pipelines/pull_request/security_solution/ai_assistant.yml
#	.buildkite/pipelines/pull_request/security_solution/asset_inventory.yml
#	.buildkite/pipelines/pull_request/security_solution/automatic_import.yml
#	.buildkite/pipelines/pull_request/security_solution/cloud_security_posture.yml
#	.buildkite/pipelines/pull_request/security_solution/cspm_agentless_scout.yml
#	.buildkite/pipelines/pull_request/security_solution/cypress_burn.yml
#	.buildkite/pipelines/pull_request/security_solution/defend_workflows.yml
#	.buildkite/pipelines/pull_request/security_solution/detection_engine.yml
#	.buildkite/pipelines/pull_request/security_solution/entity_analytics.yml
#	.buildkite/pipelines/pull_request/security_solution/explore.yml
#	.buildkite/pipelines/pull_request/security_solution/investigations.yml
#	.buildkite/pipelines/pull_request/security_solution/osquery_cypress.yml
#	.buildkite/pipelines/pull_request/security_solution/rule_management.yml
mistic added a commit to mistic/kibana that referenced this pull request Jan 31, 2026
Closes elastic/kibana-operations#414

This PR declares spotZones to be used on preemptible machine based jobs
according to data we have of zones that historically have been failing
the most over the past couple months.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
(cherry picked from commit 7c88eee)

# Conflicts:
#	.buildkite/ftr_security_stateful_configs.yml
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/agent_builder_smoke_tests.yml
#	.buildkite/pipelines/pull_request/base.yml
#	.buildkite/pipelines/pull_request/profiling_cypress.yml
#	.buildkite/pipelines/pull_request/security_solution/ai4dsoc.yml
#	.buildkite/pipelines/pull_request/security_solution/ai_assistant.yml
#	.buildkite/pipelines/pull_request/security_solution/asset_inventory.yml
#	.buildkite/pipelines/pull_request/security_solution/automatic_import.yml
#	.buildkite/pipelines/pull_request/security_solution/cloud_security_posture.yml
#	.buildkite/pipelines/pull_request/security_solution/cypress_burn.yml
#	.buildkite/pipelines/pull_request/security_solution/defend_workflows.yml
#	.buildkite/pipelines/pull_request/security_solution/detection_engine.yml
#	.buildkite/pipelines/pull_request/security_solution/entity_analytics.yml
#	.buildkite/pipelines/pull_request/security_solution/explore.yml
#	.buildkite/pipelines/pull_request/security_solution/investigations.yml
#	.buildkite/pipelines/pull_request/security_solution/osquery_cypress.yml
#	.buildkite/pipelines/pull_request/security_solution/rule_management.yml
mistic added a commit to mistic/kibana that referenced this pull request Jan 31, 2026
Closes elastic/kibana-operations#414

This PR declares spotZones to be used on preemptible machine based jobs
according to data we have of zones that historically have been failing
the most over the past couple months.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
(cherry picked from commit 7c88eee)

# Conflicts:
#	.buildkite/ftr_security_stateful_configs.yml
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/agent_builder_smoke_tests.yml
#	.buildkite/pipelines/pull_request/base.yml
#	.buildkite/pipelines/pull_request/check_saved_objects.yml
#	.buildkite/pipelines/pull_request/profiling_cypress.yml
#	.buildkite/pipelines/pull_request/prompt_changes.yml
#	.buildkite/pipelines/pull_request/security_solution/ai4dsoc.yml
#	.buildkite/pipelines/pull_request/security_solution/ai_assistant.yml
#	.buildkite/pipelines/pull_request/security_solution/asset_inventory.yml
#	.buildkite/pipelines/pull_request/security_solution/automatic_import.yml
#	.buildkite/pipelines/pull_request/security_solution/cloud_security_posture.yml
#	.buildkite/pipelines/pull_request/security_solution/cypress_burn.yml
#	.buildkite/pipelines/pull_request/security_solution/defend_workflows.yml
#	.buildkite/pipelines/pull_request/security_solution/detection_engine.yml
#	.buildkite/pipelines/pull_request/security_solution/entity_analytics.yml
#	.buildkite/pipelines/pull_request/security_solution/explore.yml
#	.buildkite/pipelines/pull_request/security_solution/investigations.yml
#	.buildkite/pipelines/pull_request/security_solution/osquery_cypress.yml
#	.buildkite/pipelines/pull_request/security_solution/rule_management.yml
mistic added a commit to mistic/kibana that referenced this pull request Jan 31, 2026
Closes elastic/kibana-operations#414

This PR declares spotZones to be used on preemptible machine based jobs
according to data we have of zones that historically have been failing
the most over the past couple months.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
(cherry picked from commit 7c88eee)

# Conflicts:
#	.buildkite/ftr_security_stateful_configs.yml
#	.buildkite/pipelines/on_merge.yml
#	.buildkite/pipelines/pull_request/agent_builder_smoke_tests.yml
#	.buildkite/pipelines/pull_request/base.yml
#	.buildkite/pipelines/pull_request/check_saved_objects.yml
#	.buildkite/pipelines/pull_request/profiling_cypress.yml
#	.buildkite/pipelines/pull_request/prompt_changes.yml
#	.buildkite/pipelines/pull_request/security_solution/ai_assistant.yml
#	.buildkite/pipelines/pull_request/security_solution/asset_inventory.yml
#	.buildkite/pipelines/pull_request/security_solution/cypress_burn.yml
#	.buildkite/pipelines/pull_request/security_solution/defend_workflows.yml
#	.buildkite/pipelines/pull_request/security_solution/detection_engine.yml
#	.buildkite/pipelines/pull_request/security_solution/entity_analytics.yml
#	.buildkite/pipelines/pull_request/security_solution/explore.yml
#	.buildkite/pipelines/pull_request/security_solution/investigations.yml
#	.buildkite/pipelines/pull_request/security_solution/osquery_cypress.yml
#	.buildkite/pipelines/pull_request/security_solution/rule_management.yml
@mistic
Copy link
Copy Markdown
Contributor Author

mistic commented Jan 31, 2026

💚 All backports created successfully

Status Branch Result
9.3
9.2
9.1
8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

mistic added a commit that referenced this pull request Jan 31, 2026
…#251151)

# Backport

This will backport the following commits from `main` to `9.3`:
- [chore(NA): use different gcp zones for spot instances
(#248181)](#248181)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2026-01-29T15:43:53Z","message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v9.4.0"],"title":"chore(NA):
use different gcp zones for spot
instances","number":248181,"url":"https://github.com/elastic/kibana/pull/248181","mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248181","number":248181,"mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}}]}]
BACKPORT-->
mistic added a commit that referenced this pull request Jan 31, 2026
…#251153)

# Backport

This will backport the following commits from `main` to `9.1`:
- [chore(NA): use different gcp zones for spot instances
(#248181)](#248181)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2026-01-29T15:43:53Z","message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v9.4.0"],"title":"chore(NA):
use different gcp zones for spot
instances","number":248181,"url":"https://github.com/elastic/kibana/pull/248181","mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248181","number":248181,"mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}}]}]
BACKPORT-->
mistic added a commit that referenced this pull request Jan 31, 2026
#251155)

# Backport

This will backport the following commits from `main` to `8.19`:
- [chore(NA): use different gcp zones for spot instances
(#248181)](#248181)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2026-01-29T15:43:53Z","message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v9.4.0"],"title":"chore(NA):
use different gcp zones for spot
instances","number":248181,"url":"https://github.com/elastic/kibana/pull/248181","mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248181","number":248181,"mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}}]}]
BACKPORT-->
mistic added a commit that referenced this pull request Feb 1, 2026
…#251152)

# Backport

This will backport the following commits from `main` to `9.2`:
- [chore(NA): use different gcp zones for spot instances
(#248181)](#248181)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2026-01-29T15:43:53Z","message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v9.4.0"],"title":"chore(NA):
use different gcp zones for spot
instances","number":248181,"url":"https://github.com/elastic/kibana/pull/248181","mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248181","number":248181,"mergeCommit":{"message":"chore(NA):
use different gcp zones for spot instances (#248181)\n\nCloses
https://github.com/elastic/kibana-operations/issues/414\n\nThis PR
declares spotZones to be used on preemptible machine based
jobs\naccording to data we have of zones that historically have been
failing\nthe most over the past couple
months.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Tyler
Smalley
<tyler.smalley@elastic.co>","sha":"7c88eeec4f459a1af5515fbfbf7e1d38c5623acf"}}]}]
BACKPORT-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:all-open Backport to all branches that could still receive a release chore release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team v8.19.11 v9.1.11 v9.2.5 v9.3.0 v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants