Skip to content

e2e: skip the egress credential injection test - #2518

Merged
Bowei Du (bowei) merged 1 commit into
agent-substrate:mainfrom
yufan-su:e2e-skip-credinject
Oct 12, 2026
Merged

Bowei Du (bowei) merged 1 commit into
agent-substrate:mainfrom
yufan-su:e2e-skip-credinject

Conversation

@yufan-su

Copy link
Copy Markdown
Collaborator

#2513

  • Tests pass
  • Appropriate changes to documentation are included in the PR

TestActorEgressCredentialInjection fetches httpbin.org through the egress
gateway, and while httpbin.org answers 502/503 every PR fails CI regardless
of what it changes. Skip it until the echo origin runs in the cluster.
@bowei
Bowei Du (bowei) added this pull request to the merge queue Oct 12, 2026
Merged via the queue into agent-substrate:main with commit 73882a0 Oct 12, 2026
14 checks passed
Yufan Su (yufan-su) added a commit to yufan-su/substrate that referenced this pull request Oct 12, 2026
agent-substrate#2535)

agent-substrate#2513 

### Changes
- Re-enable the credential injection e2e which was skipped in agent-substrate#2518
- `testserver http` gains `/echoheaders`, which returns the request
headers it received as `{"headers": {...}}`.
- The suite deploys two echo origins in its own namespace:
- `echo-https` on 443, serving a certificate from the cluster's
service-DNS signer through a projected `podCertificate` volume. The
egress gateway trusts that signer once
`hack/setup-e2e-egress-tls-kind.sh` has run, and CI already runs it.
  - `echo-http` on 80.
- The fail-closed hosts are `.invalid` names that exist only in the
policy.
- Coverage is unchanged: injection and no-header checks over HTTPS and
plain HTTP, plus the three fail-closed cases (unfetchable secret,
unserved provider, unauthorized namespace) on both schemes.

### Testing


- [x] Tests pass
- [ ] Appropriate changes to documentation are included in the PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants