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
Envoy 1.21.0 brought a new wildcard definition (itself related to odcds)
While it seems that envoy will not use this new model out of odcds for now, the go-control-plane should support it as there is no strong commitment in the xds protocol, and to allow users to use odcds
A few specific considerations:
a stream can now define subscribing to wildcard by sending "*" instead of nothing
a stream can now subscribe or unsubscribe from wildcard while still referencing resources, and it expects the control-plane to keep track of explicitly subscribed resources
when unsubscribing from a specific resource while using a wildcard subscription, envoy expects the control-plane to return the state of such resource
The text was updated successfully, but these errors were encountered:
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.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Envoy 1.21.0 brought a new wildcard definition (itself related to odcds)
While it seems that envoy will not use this new model out of odcds for now, the go-control-plane should support it as there is no strong commitment in the xds protocol, and to allow users to use odcds
A few specific considerations:
The text was updated successfully, but these errors were encountered: