-
Notifications
You must be signed in to change notification settings - Fork 867
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
feat(experiments): add ability to set service port mappings #3544
base: master
Are you sure you want to change the base?
Conversation
Go Published Test Results2 160 tests 2 160 ✅ 2m 53s ⏱️ Results for commit 4a99969. ♻️ This comment has been updated with latest results. |
E2E Tests Published Test Results 4 files 4 suites 3h 29m 2s ⏱️ For more details on these failures, see this check. Results for commit 4a99969. ♻️ This comment has been updated with latest results. |
9f31bbd
to
ed8aa29
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3544 +/- ##
==========================================
- Coverage 83.86% 83.85% -0.01%
==========================================
Files 163 163
Lines 18560 18577 +17
==========================================
+ Hits 15565 15578 +13
- Misses 2121 2123 +2
- Partials 874 876 +2 ☔ View full report in Codecov by Sentry. |
ed8aa29
to
74a6051
Compare
👋 @zachaller not sure why the code coverage dropped. I added an e2e test that covers the new code paths 🤔 |
Quality Gate passedIssues Measures |
docs/features/experiment.md
Outdated
@@ -57,6 +57,11 @@ spec: | |||
service: | |||
# Name of the Service (optional). If omitted, service: {} would also be acceptable. | |||
name: service-name | |||
# Service port mappings(optional). This is useful when the container port is different from the desired service port. | |||
# If omitted, the port will be mapped to the container port. | |||
portMappings: |
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.
why not just go with ports
to keep it consistent with how we write a service in k8s?
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.
I agree with this, we need to be forward thinking in possibly embeding the whole service spec and to do that we would want to match it's api.
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.
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.
thanks for the review guys. I'll have a look asap.
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.
@meeech @zachaller done! I amended my previous commits.
4a99969
to
d45468f
Compare
Published E2E Test Results4 files 4 suites 0s ⏱️ For more details on these failures, see this check. Results for commit 1a0a89a. ♻️ This comment has been updated with latest results. |
Published Unit Test Results2 261 tests 2 259 ✅ 2m 56s ⏱️ For more details on these failures, see this check. Results for commit 1a0a89a. ♻️ This comment has been updated with latest results. |
Signed-off-by: Yohan Belval <[email protected]>
d45468f
to
5b4a1a7
Compare
629c3bd
to
9b86988
Compare
Signed-off-by: Yohan Belval <[email protected]>
9b86988
to
1a0a89a
Compare
Quality Gate passedIssues Measures |
Adds enhancement #3428
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.