joshsiv-mulga a0b3b8af32 ci: select e2e suites by allow-list instead of deny-list ...

Both jobs filtered SUITES by exclusion, so any suite named in neither
deny-list ran in both jobs. That is how lb came to run twice per e2e run,
and it makes adding a suite silently fan it out everywhere.

Each job now names the suites it is eligible to run. Selection is still
driven by SUITES, so this is behaviour-preserving for the current default:
single/iam/cert on the single-node job, multinode/lb/cert on the multi-node
job, exactly as before. eks, ecs and storagegrowth are listed as eligible on
the single-node job but are not yet in the default SUITES.

2026-07-20 14:18:43 +10:00

..

actions

feat(eks): multinode control-plane + IMDS/token-webhook CP fixes (426/427/428/495/496) (#459)

2026-07-09 09:43:30 +10:00

assets

Rewrite README key sections and banner in the site voice

2026-07-16 12:39:44 -05:00

scripts

fix(network): IGW route-table AWS parity + per-subnet egress gating (#270)

2026-06-01 09:54:29 +10:00

workflows

ci: select e2e suites by allow-list instead of deny-list

2026-07-20 14:18:43 +10:00

CODEOWNERS

fix: remove falltrhough code owners

2026-06-05 09:08:42 +10:00

dependabot.yml

fix: min package age 3 days

2026-05-12 11:23:58 +10:00

pull_request_template.md

chore: switch to single default PR template

2026-06-19 11:22:36 +10:00

resolve-sibling-refs.sh

ci: build sibling repos from a co-named branch, falling back to dev (#550)

2026-07-19 14:30:13 +10:00