kubernetes-sigs / kubernetes-sigs/gateway-api
Conditions for Policy Attachment
Open
help wanted
kind/feature
lifecycle/frozen
priority/backlog
- Dominant language
- Go
- Stars
- 3k
- Forks
- 789
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 45
Description
**What would you like to be added**:
As discussed in https://github.com/kubernetes-sigs/gateway-api/pull/715#discussion_r672724388 and https://github.com/kubernetes-sigs/gateway-api/issues/590, any form of status per policy is going to be complex. These conditions may need to be per controller or even per referencing resource (ie policy targeting Route that is also targeted by several Gateways).
**Why this is needed**:
Although each implementation can currently take whichever approach makes the most sense for them, it would be better to standardize on this.
GEP: #713
Contributor guide
Assessment
This issue has not been assessed yet.