You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
This GEP attempts to tackle both cross namespace forwarding and route inclusion (proposed earlier by @stevesloka). These are closely related concepts that can likely be solved with the ReferencePolicy concept originally proposed by @youngnick.
Why is this needed:
Both cross namespace forwarding and route inclusion are common feature requests. ReferencePolicy provides a way to safely accomplish this. This is closely related to #411, #582, and #634.
What would you like to be added:
This GEP attempts to tackle both cross namespace forwarding and route inclusion (proposed earlier by @stevesloka). These are closely related concepts that can likely be solved with the ReferencePolicy concept originally proposed by @youngnick.
Why is this needed:
Both cross namespace forwarding and route inclusion are common feature requests. ReferencePolicy provides a way to safely accomplish this. This is closely related to #411, #582, and #634.
Relevant docs include:
Note: Although the Gateway -> Route relationship is closely related to this discussion, I've decided to tackle that in a later GEP.
The text was updated successfully, but these errors were encountered: