ci: run federated edge e2e against real Karmada#280
Merged
Conversation
Add a CI job that stands up the production-fidelity edge — two kind clusters wired with real Karmada federation, the production Envoy Gateway version, the Coraza WAF data plane, and the NSO extension server — and drives the edge e2e scenarios through real traffic. The existing test-e2e.yml only runs the non-federated test/e2e suite; the edge scenarios and the federation delivery path had no CI coverage. This is the last remaining piece of the #247 stack (#224-#228, #276 all landed on main); the workflow now collapses to a single file plus the tool-install task its steps depend on. Key changes: - Add .github/workflows/test-e2e-federated.yml: free disk + raise inotify limits for the Karmada footprint, install pinned tools, bring up the env, stand up Karmada, run the edge scenarios, dump cross-cluster diagnostics on failure - Add a test-infra:tools task that installs the pinned binaries the env needs (kind, karmadactl, kustomize, cmctl, chainsaw) so CI and a clean checkout no longer rely on hand-placed binaries; karmadactl is pulled as a release binary because its go.mod replace directives block go install
kevwilliams
approved these changes
Jul 15, 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
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.
Rebase of #248 onto
main. The rest of the #247 stack (#224, #225, #226, #227, #228, #276) has landed, so this collapses to the one piece still missing: the federated CI job and the tool-install task it depends on.What this adds
.github/workflows/test-e2e-federated.yml— CI job that stands up the prod-fidelity edge (two kind clusters, real Karmada, EG v1.7.4, Coraza WAF, NSO extension server) and runs thetest/e2e-edge/scenarios against real traffic. Frees runner disk, raises inotify limits, dumps cross-cluster diagnostics on failure.Taskfile.test-infra.yml— atest-infra:toolstask installing the pinned binaries (kind v0.32.0, karmadactl v1.15.2, kustomize, cmctl, chainsaw).karmada-upalready invokedbin/karmadactlbut nothing installed it; this closes the repro gap so CI and a clean checkout come up without hand-placed binaries.Why the diff is small
The edge scenarios (
test/e2e-edge/) and the federation path (config/federation/, #227) had no CI coverage — the "not yet wired into CI" follow-up from #247. The env tasks it builds on (up,karmada-up,e2e) are already onmain; only the workflow and the tool task are new.Verification
task test-infra:toolsruns clean locally — all five binaries install and execute.Supersedes #248. Closes the last open child of #247.