-
Notifications
You must be signed in to change notification settings - Fork 204
ci: update all n1-standard-4 type runners to n2-standard-4 #8340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pkoutsovasilis
merged 1 commit into
elastic:main
from
pkoutsovasilis:ci/update_vm_runners
Jun 5, 2025
Merged
ci: update all n1-standard-4 type runners to n2-standard-4 #8340
pkoutsovasilis
merged 1 commit into
elastic:main
from
pkoutsovasilis:ci/update_vm_runners
Jun 5, 2025
Conversation
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
|
Contributor
💚 Build Succeeded
|
v1v
approved these changes
Jun 5, 2025
dliappis
approved these changes
Jun 5, 2025
Contributor
dliappis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Contributor
|
@Mergifyio backport 8.17 8.18 8.19 9.0 |
Contributor
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Jun 5, 2025
(cherry picked from commit f08681f)
mergify bot
pushed a commit
that referenced
this pull request
Jun 5, 2025
(cherry picked from commit f08681f)
8 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jun 5, 2025
(cherry picked from commit f08681f)
This was referenced Jun 5, 2025
mergify bot
pushed a commit
that referenced
this pull request
Jun 5, 2025
(cherry picked from commit f08681f)
8 tasks
pkoutsovasilis
added a commit
that referenced
this pull request
Jun 5, 2025
pkoutsovasilis
added a commit
that referenced
this pull request
Jun 5, 2025
pkoutsovasilis
added a commit
that referenced
this pull request
Jun 5, 2025
v1v
added a commit
to v1v/elastic-agent
that referenced
this pull request
Jun 5, 2025
* main: Remove cloudbeat from CODEOWNERS (elastic#8336) fix(ci): restore `go mod tidy` in `otel-update.sh` script (elastic#8326) ci: update all n1-standard-4 type runners to n2-standard-4 (elastic#8340) build(deps): bump github.com/elastic/go-concert from 0.3.0 to 0.3.1 (elastic#8313) ci: add retries when rendering kustomize (elastic#8321) [main][Automation] Update versions (elastic#8318) feat: generate a subject key identifier when creating a certificate (elastic#6379) otel: support system/metrics input with experimental otel runtime (elastic#8148) ci: update all n1-standard-8 type runners to n2-standard-8 (elastic#8320) build(deps): bump github.com/elastic/elastic-agent-libs from 0.19.5 to 0.19.6 (elastic#8283)
pkoutsovasilis
added a commit
that referenced
this pull request
Jun 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.





What does this PR do?
This PR updates the machine type for a Buildkite pipeline step in
.buildkite/bk.integration.pipeline.yml, changing it fromn1-standard-4ton2-standard-4.Why is it important?
The
n1machine series on GCP is older, with inferior performance and cost efficiency compared to the newern2series. Moving ton2-standard-4aligns with the improvements adopted in previous CI upgrades (e.g.,n2-standard-8), offering better resource availability and stability in CI jobs.This change also ensures consistency across Buildkite steps and prepares us for any potential future deprecation of
n1machine types by GCP.Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None. This is a CI-only change and has no impact on the Elastic Agent runtime behavior, packaging, or user-facing interfaces.
How to test this PR locally
This change affects CI configuration only. The pipeline will be automatically exercised when the Buildkite job runs.
Related issues
n2series for improved performance and consistency