-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
connect: update supported envoy versions to 1.18.2, 1.17.2, 1.16.3, and 1.15.4 #10101
Conversation
@@ -642,6 +643,7 @@ func TestClustersFromSnapshot(t *testing.T) { | |||
} | |||
|
|||
latestEnvoyVersion := proxysupport.EnvoyVersions[0] | |||
latestEnvoyVersion_v2 := proxysupport.EnvoyVersionsV2[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realized when I went to update these golden tests that my last refactor hadn't accounted for skipping v2-compat
tests for >= 1.17.x
. All of the golden tests got similar adjustments.
@@ -28,6 +28,13 @@ | |||
"routeConfigName": "db" | |||
}, | |||
"httpFilters": [ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
an actual difference
@@ -28,6 +28,13 @@ | |||
"routeConfigName": "db" | |||
}, | |||
"httpFilters": [ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
an actual difference
| 1.9.x | 1.16.3, 1.15.4, 1.14.7‡, 1.13.8‡ | | ||
| 1.8.x | 1.14.7, 1.13.8, 1.12.7, 1.11.2 | | ||
| 1.7.x | 1.13.8, 1.12.7, 1.11.2, 1.10.0\* | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The manual backports of this pr to the older series will finish making these 3 lines true.
ce361b6
to
2d6c051
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we use test-envoy-versions.sh
anywhere? Just saw it wasn't updated, but maybe can be deleted.
@freddygv deleting the debugging file |
Co-authored-by: Freddy <[email protected]>
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/360035. |
🍒✅ Cherry pick of commit abc1dc0 onto |
…nd 1.15.4 (#10101) The only thing that needed fixing up pertained to this section of the 1.18.x release notes: > grpc_stats: the default value for stats_for_all_methods is switched from true to false, in order to avoid possible memory exhaustion due to an untrusted downstream sending a large number of unique method names. The previous default value was deprecated in version 1.14.0. This only changes the behavior when the value is not set. The previous behavior can be used by setting the value to true. This behavior change by be overridden by setting runtime feature envoy.deprecated_features.grpc_stats_filter_enable_stats_for_all_methods_by_default. For now to maintain status-quo I'm explicitly setting `stats_for_all_methods=true` in all versions to avoid relying upon the default. Additionally the naming of the emitted metrics for these gRPC requests changed slightly so the integration test assertions for `case-grpc` needed adjusting.
The only thing that needed fixing up pertained to this section of the 1.18.x release notes:
For now to maintain status-quo I'm explicitly setting
stats_for_all_methods=true
in all versions to avoid relying upon the default.Additionally the naming of the emitted metrics for these gRPC requests changed slightly so the integration test assertions for
case-grpc
needed adjusting.