-
Notifications
You must be signed in to change notification settings - Fork 288
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
Internal Data Model Design and Implementation #32
Comments
For reference, Contour's internal data model ("the DAG"), which all APIs (Gateway API, Ingress, HTTPProxy) are converted to before emitting Envoy config, is defined here: https://github.com/projectcontour/contour/blob/main/internal/dag/dag.go |
Reassigned to @arkodg |
Relates to envoyproxy#32 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
Relates to envoyproxy#32 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
* [ir] Init Structure Relates to #32 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
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. |
The initial Xds and Infra IRs have been developed so I'm closing this issue. |
#16 specifies the need for an Intermediate Representation (IR) component to decouple the system from Gateway API. The IR details should be captured in this issue or a linked doc.
The text was updated successfully, but these errors were encountered: