feat(kuma-cp) transparent proxy v3 #1399
Merged
Conversation
This file contains 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
jakubdyszkiewicz
force-pushed
the
chore/proxy-template-v3
branch
from
a164fa7
to
d1795d7
Compare
jakubdyszkiewicz
force-pushed
the
feat/transparent-proxy-v3
branch
from
0f12bb6
to
1bc0cb2
Compare
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
jakubdyszkiewicz
force-pushed
the
feat/transparent-proxy-v3
branch
from
1bc0cb2
to
651c0a0
Compare
|
This one is not to be backported, AFAIK. |
nickolaev
approved these changes
Jan 15, 2021
lobkovilya
approved these changes
Jan 15, 2021
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.
Summary
This PR uses restores support for transparent proxy in V3.
To do this we had to upgrade to Envoy 1.17 (done) and use new Envoy config that has bind_to_port undeprecated.
For those new proto I had to upgrade the go-control-plane to the newest version from master. They introduced changes in Snapshot so I had to update our modified Snapshot as an interface.
Documentation