-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEP: Provide a standard way to configure per-Gateway Infrastructure #1867
Comments
/assign |
Leaving this open until this GEP either graduates to standard or is removed from the API. /kind gep |
@robscott: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/assign @mikemorris |
/assign @keithmattix |
Action items for standard:
|
Implementations: Istio, Envoy Gateway,? Is anyone aware of more? |
Cilium also supports labels and annotations in infrastructure. |
Gloo Gateway supports attaching implementation-specific config to a |
I think the only tasks left before this gets closed out is to bump some API types |
Yes, we will need to remove the experimental tags from the |
What would you like to be added: a standard way to configure per-Gateway Infrastructure
Why this is needed: Currently this is only configurable on a Cluster scoped resource, which has a variety of issues
GEP: #1868
The text was updated successfully, but these errors were encountered: