Feat/l4 routing #527
Merged
Feat/l4 routing #527
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
This commit adds beta support for L4 routing using TCPIngress Custom Resource. Plain TCP port based routing and SNI-based routing for TLS over TCP are supported. Annotations for KongIngress are supported on TCPIngress resource as well to change the protocols for the corresponding route, however, that should be rarely required. Documentation will follow in a separate commit in future.
hbagdi
force-pushed
the
feat/l4-routing
branch
from
c4c165b
to
72af831
Compare
|
Is this already released? Is there documentation for this? |
|
This is part of 0.8 release happening this Thursday. |
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.
Add beta support for L4 routing using TCPIngress
Custom Resource.
Plain TCP port based routing and SNI-based routing for TLS over TCP are
supported.
Annotations for KongIngress are supported on TCPIngress resource as
well to change the protocols for the corresponding route, however, that
should be rarely required.
Documentation will follow in a separate commit in future.
Fix #343