ci(e2e): retry kind cluster bring-up to absorb runner flakes#41
Merged
Conversation
The e2e legs intermittently failed inside helm/kind-action itself (the kind cluster never came up: image pulls / control-plane wait timing out), which is unrelated to the code under test. Install the kind tooling only, then create the cluster ourselves wrapped in a 3-attempt retry. Both engine legs pass reliably once the cluster is up; this just stops the bring-up flake from reddening them.
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
1 participant
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.
Why
After the per-engine e2e split, both legs pass reliably when the kind cluster comes up (verified: knative + keda
Run e2e testsbothsuccess). The remaining red legs werehelm/kind-action@v1failing during cluster creation itself — a hosted-runner flake (image pulls / control-plane--wait), not our code.What
Use
helm/kind-actionininstall_onlymode (just the kind/kubectl tooling), then create the cluster ourselves wrapped in a 3-attemptnick-fields/retry. Cluster name (elpio-dev) still comes fromtests/e2e/kind-config.yaml. e2e stays non-blocking; this just cuts the bring-up flake rate.