[9.1] chore(NA): use different gcp zones for spot instances (#248181)#251153
Merged
mistic merged 1 commit intoelastic:9.1from Jan 31, 2026
Merged
[9.1] chore(NA): use different gcp zones for spot instances (#248181)#251153mistic merged 1 commit intoelastic:9.1from
mistic merged 1 commit intoelastic:9.1from
Conversation
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
Contributor
💚 Build Succeeded
Metrics [docs]
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto9.1:Questions ?
Please refer to the Backport tool documentation