Use embedded etcd for scale test cluster#624
Merged
shayasoolin merged 1 commit intoMay 19, 2026
Merged
Conversation
Ronkahn21
approved these changes
May 19, 2026
danbar2
reviewed
May 19, 2026
danbar2
approved these changes
May 19, 2026
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
3 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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
This updates the k3d cluster created by the e2e infra manager to start the single k3s server with embedded etcd:
The scale test creates enough pod and status churn that the default single-server k3s datastore, sqlite through kine, can lag under CI load. In the failed scale CI runs, the API server showed symptoms such as stale resource versions, compacted revisions, handler timeouts, and list/watch calls stalling while the scale test waited for pods to become ready.
--cluster-init@server:0keeps the same single-server k3d topology, but bootstraps the k3s server with embedded etcd as the datastore instead of sqlite/kine. This gives the scale test a datastore path that handles the high watch/list/update churn more reliably.Which issue(s) this PR fixes:
Related to #550
Special notes for your reviewer:
This is intentionally scoped to cluster creation. It does not change the scale test workload, node count, controller settings, or workflow behavior.
Does this PR introduce a API change?
Additional documentation e.g., enhancement proposals, usage docs, etc.: