-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ws-daemon] Add ws-daemon headless service #3473
Conversation
7080be3
to
5966598
Compare
Thx for your contribution @rl-gitpod ! Approach and implementation look good to me. @csweichel ? |
@rl-gitpod, why not just replace/improve/fix the current approach? Adding an option without any additional check for the CNI will lead to the same restriction and problems. |
@aledbf - not sure I follow. I agree that there is a much bigger and potentially more impactful aspect of using the nodePort and the existing wso.HostIP() elsewhere throughout the code base - which is perhaps what you are referring to? If so, that was the thinking but beyond the scope of this issue and I'm unsure of where that fits in the short/medium term. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/werft run 👍 started the job as gitpod-build-rl-2956-no-ws-daemon-nodeport.2 |
@csweichel friendly ping |
/werft run 👍 started the job as gitpod-build-rl-2956-no-ws-daemon-nodeport.3 |
Use endpoint on the ws-manager node to avoid pod/nodePort access issues.
5966598
to
b8a63c2
Compare
/werft run 👍 started the job as gitpod-build-rl-2956-no-ws-daemon-nodeport.8 |
1b56704
to
40ec397
Compare
Codecov Report
@@ Coverage Diff @@
## main #3473 +/- ##
=========================================
+ Coverage 0 37.07% +37.07%
=========================================
Files 0 14 +14
Lines 0 3903 +3903
=========================================
+ Hits 0 1447 +1447
- Misses 0 2337 +2337
- Partials 0 119 +119
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM
Use endpoint on the ws-manager node to avoid pod/nodePort access issues.
Addresses #2956