envoyproxy / envoyproxy/gateway
Custom policy attachment status reporting doc
- Dominant language
- Go
- Stars
- 3k
- Forks
- 864
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 140
Description
*Description*:
Envoy Gateway supports custom policy attachments via Extension server (see example [here](https://gateway.envoyproxy.io/latest/tasks/extensibility/extension-server/)). But it is not clear how the status for the policy attachment be updated.
Ask of this issue is to have a companion doc to EG [extensions design](https://gateway.envoyproxy.io/contributions/design/extending-envoy-gateway/) which details to a vendor authoring custom policies on how to leverage EG extension server to do status reporting for their custom policies.
Looking thru [GEP-713](https://gateway-api.sigs.k8s.io/geps/gep-713), the status reporting on the policy attachments seems like can get very complicated with multiple options floated.
Perhaps we can start with "Standard status struct" scenario ([reference](https://gateway-api.sigs.k8s.io/geps/gep-713/#standard-status-struct)) which is what `BackendTLSPolicy` follows.
[optional *Relevant Links*:]
>Any extra documentation required to understand the issue.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.