-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: Add initial support for SSL termination for TransportServer #3462
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
Conversation
fc1bd9b
to
aa8f68c
Compare
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #3462 +/- ##
==========================================
+ Coverage 52.17% 52.25% +0.08%
==========================================
Files 59 59
Lines 16772 16834 +62
==========================================
+ Hits 8750 8797 +47
- Misses 7727 7740 +13
- Partials 295 297 +2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
d8c03af
to
91c1740
Compare
91c1740
to
0d2c233
Compare
0d2c233
to
a1962c7
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.
This looks good. I have a few items that we can look at to your design document for additional items to add down the road.
a1962c7
to
e59ba83
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.
👍
e59ba83
to
738d784
Compare
880ea6b
to
6ee37c0
Compare
Proposed changes
Add initial support for SSL termination for TransportServer. Note this PR supports TLS termination on multiple ports, where each application owns a dedicated port: the Ingress Controller terminates TLS connections on each port, where each application uses its own cert/key, and routes connections to appropriate application (service) based on that incoming port (any TLS connection regardless of the SNI on a port will be routed to the application that corresponds to that port). Future work will include support for routing TCP connections to an appropriate application (service) based on the SNI of the connection.
Checklist
Before creating a PR, run through this checklist and mark each as complete.