Fix deprecated envoy name warnings #8425
Assignees
Labels
theme/envoy/xds
Related to Envoy support
Comments
rboyer
added a commit
that referenced
this issue
Feb 11, 2021
Note that this does NOT upgrade to xDS v3. That will come in a future PR. Additionally: - Ignored staticcheck warnings about how github.com/golang/protobuf is deprecated. - Shuffled some agent/xds imports in advance of a later xDS v3 upgrade. - Remove support for envoy 1.13.x but don't add in 1.17.x yet. We have to wait until the xDS v3 support is added in a follow-up PR. Fixes #8425
rboyer
added a commit
that referenced
this issue
Feb 19, 2021
Note that this does NOT upgrade to xDS v3. That will come in a future PR. Additionally: - Ignored staticcheck warnings about how github.com/golang/protobuf is deprecated. - Shuffled some agent/xds imports in advance of a later xDS v3 upgrade. - Remove support for envoy 1.13.x but don't add in 1.17.x yet. We have to wait until the xDS v3 support is added in a follow-up PR. Fixes #8425
rboyer
added a commit
that referenced
this issue
Feb 22, 2021
Note that this does NOT upgrade to xDS v3. That will come in a future PR. Additionally: - Ignored staticcheck warnings about how github.com/golang/protobuf is deprecated. - Shuffled some agent/xds imports in advance of a later xDS v3 upgrade. - Remove support for envoy 1.13.x but don't add in 1.17.x yet. We have to wait until the xDS v3 support is added in a follow-up PR. Fixes #8425
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since #8424 changed the supported min envoy version to
v1.12.xI think we should be able to resolve a bunch of the following envoy deprecation warnings easily with a straight replacement.If any of these deprecations were introduced after
v1.12.xfixing these will require using the version sniffing logic recently added.Deprecation Info:
https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated
Note this list is likely incomplete. For simplistic mesh scenarios these were just the first several that showed up in the envoy logs:
Cluster Fields
envoy.deprecated_features:envoy.api.v2.Cluster.tls_context: trueUsing runtime overrides to continue using now fatal-by-default deprecated option 'envoy.api.v2.Cluster.tls_context' from file cluster.proto.Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cluster.proto.HTTP
envoy.deprecated_features:envoy.config.trace.v2.ZipkinConfig.HTTP_JSON_V1: trueenvoy.deprecated_features:envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing.operation_name: trueUsing runtime overrides to continue using now fatal-by-default deprecated option 'envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager.Tracing.operation_name' from file http_connection_manager.proto.Listener Fields
Using deprecated option 'envoy.api.v2.listener.FilterChain.tls_context' from file listener_components.proto.Using deprecated option 'envoy.api.v2.listener.Filter.config' from file listener_components.proto.Extension Names
Using deprecated extension name 'envoy.tcp_proxy' for 'envoy.filters.network.tcp_proxy'.Using deprecated extension name 'envoy.http_connection_manager' for 'envoy.filters.network.http_connection_manager'Using deprecated extension name 'envoy.router' for 'envoy.filters.http.router'.The text was updated successfully, but these errors were encountered: