-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat: k8s custom port expose #3449
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
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
… into feat-k8s-custom-port-expose
Codecov Report
@@ Coverage Diff @@
## master #3449 +/- ##
==========================================
+ Coverage 90.43% 90.52% +0.09%
==========================================
Files 152 152
Lines 11009 11020 +11
==========================================
+ Hits 9956 9976 +20
+ Misses 1053 1044 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Currently, the only possible port to reach the k8s gateway is 8080.
This pr makes it possible to specify the port number in the flow