-
Notifications
You must be signed in to change notification settings - Fork 679
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
Add support for Envoy xDS v3. #1898
Comments
Related to #2132 |
According to https://www.envoyproxy.io/docs/envoy/latest/api/api_supported_versions, the V2 API will stop being supported at the end of this year. Seeing this issue is unprioritized, is Contour at risk of falling too far behind? |
We should move this into Prioritized -- we're aware of the EOY deprecation deadline and are working towards adding v3 support. |
I'm going to poke around a bit to see how we might address this migration. |
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the contour package into a v2 package for Envoy API V2 types. Common items are kept in the contour package for use by other versions. This doesn't change anything functionally, just refactors contour into a v2 package. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the contour package into a v2 package for Envoy API V2 types. Common items are kept in the contour package for use by other versions. This doesn't change anything functionally, just refactors contour into a v2 package. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the featuretests package into a v2 package for Envoy API V2 types. Common items are kept in the feature package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the envoy package into a v2 package for Envoy API V2 types. Common items are kept in the envoy package for use by other versions. Updates: #1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Refactors the contour package into a v2 package for Envoy API V2 types. Common items are kept in the contour package for use by other versions. This doesn't change anything functionally, just refactors contour into a v2 package. Updates: projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Drop support for xDS v3 resource version by changing the default boostrap resource version to v3 and removing the v2 xDS resource server. Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Enables v3 xDS Clusters as well as supporting structs. Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Enables v3 xDS Clusters as well as supporting structs. Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
…oy/v3/endpoints Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Switches from v2 xds caches to v3 xds caches for observing the DAG and backing the v3 xDS server. Updates projectcontour#1898. Signed-off-by: Steve Kriss <krisss@vmware.com>
Updates #1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
internal: switch from v2 to v3 xDS caches Switches from v2 xds caches to v3 xds caches for observing the DAG and backing the v3 xDS server. Updates #1898 Signed-off-by: Steve Kriss <krisss@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates #1898 Signed-off-by: Steve Sloka <slokas@vmware.com>
Updates projectcontour#1898. Signed-off-by: Steve Kriss <krisss@vmware.com>
Updates #1898. Signed-off-by: Steve Kriss <krisss@vmware.com>
@stevesloka think we can consider this closed now? |
Yup I think so! 🎉 |
A year after Envoy ships xDS v3, they plan to remove support for v2. It's not entirely clear to me what that entails, but it seems likely we will need to add and qualify v3 support and maybe support v2 at the same time.
See envoyproxy/envoy#6271
The text was updated successfully, but these errors were encountered: