-
Notifications
You must be signed in to change notification settings - Fork 287
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
Initial Resource Translator Design and Implementation #38
Comments
For reference, Contour's Gateway API translation logic is largely contained here: https://github.com/projectcontour/contour/blob/main/internal/dag/gatewayapi_processor.go |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
#145 resolves the design portion of this issue. |
Updates envoyproxy#38. Signed-off-by: Steve Kriss <krisss@vmware.com>
* Adds initial draft of Gateway API translator Updates #38. Signed-off-by: Steve Kriss <krisss@vmware.com> * Cache interface -> Resources struct Signed-off-by: Steve Kriss <krisss@vmware.com> * set unique names for IR routes Signed-off-by: Steve Kriss <krisss@vmware.com>
#16 specifies the need for a Gateway API Translator (GAT) to decouple the user APIs from the internal system. The GAT details should be captured in this issue or a linked doc.
The text was updated successfully, but these errors were encountered: