Skip to content

docs: network-egress.md describes the actor certificate checks the egress gateway makes - #3716

Open
Eric Curtin (ericcurtin) wants to merge 2 commits into
agent-substrate:mainfrom
ericcurtin:egress-doc-cert-checks
Open

Eric Curtin (ericcurtin) wants to merge 2 commits into
agent-substrate:mainfrom
ericcurtin:egress-doc-cert-checks

Conversation

@ericcurtin

Copy link
Copy Markdown
Contributor

The guide said the PEP must read the ActorIdentity extension, require the atunnel purpose and match the actor UID. verifyActorCertificate and validateActor do none of these. The guide now states what is checked and the name reuse limitation.

Fixes #3709

AI use: AI-assisted. I checked the text against egress.go.

  • Tests pass
  • Docs updated

The guide required an ActorIdentity extension, the atunnel purpose and a UID
match. The egress gateway checks none of them.

Signed-off-by: Eric Curtin <eric.curtin@docker.com>
@ericcurtin

Copy link
Copy Markdown
Contributor Author

Julian Gutierrez Oschmann (@juli4n) Max Thompson (@thompsonmax) PTAL when you have a moment, thank you! The failing envoy e2e job is TestRequestParking, unrelated to this docs change.

Signed-off-by: Eric Curtin <eric.curtin@docker.com>

This branch has not been deployed

No deployments
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.

network-egress.md describes actor certificate checks the egress gateway doesn't make

1 participant