-
Notifications
You must be signed in to change notification settings - Fork 482
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: DNS configuration as part of Gateway API #2627
Comments
@maleck13 was it your intention to personally start the initial provisional PR? |
Yes, I would be happy to put a provision GEP in place expanding on the What and Why |
Awesome! /assign @maleck13 Please let us know if you get stuck, have questions, or otherwise need support in moving this forward! 🖖 |
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 |
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 |
This is a GEP tracking issue
What would you like to be added:
A GEP to propose a solution for configuring DNS requirements and configuration associated with a gateway
Why this is needed:
Based on discussion #2541 there is interest is potentially solving DNS configuration within Gateway API. The discussion and initial GEP will expand on the What and WHY
The text was updated successfully, but these errors were encountered: