Revert "Enable to track request response size statistics (#2160)" #2162
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit cf502d5.
Collaborator
|
Code coverage for golang is |
Member
|
Thx for clarifying 👍 |
Collaborator
|
This pull request is APPROVED by Approvers can cancel the approval by writing |
Member
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit cf502d5.
What this PR does / why we need it:
Seems like the config field
track_cluster_statsis supported only for V3 API introduced from v1.13. On the other hand our current version of Envoy is 1.10 which supports only v2 API.Currently, the latest version of
pipecd-gatewayis unavailable due to unable to parse the config so this PR reverts for now. But either way, we'd better bump Envoy to after v1.13 (current latest is v1.19) as soon as possible because V2 API is no longer supported.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: