feat(ws): setup virtualservice to route traffic to relevant workspace #500
Conversation
This file contains hidden or 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
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
google-oss-prow
bot
added
area/controller
google-oss-prow
bot
requested review from
andyatmiami,
kimwnasptd and
thesuperzapper
harshad16
changed the title
harshad16
force-pushed
the
virtualservice
branch
2 times, most recently
from
4dcf94e to
50b6026
Compare
|
/ok-to-test |
- Update the helper func with CopyDeepVirtualService Signed-off-by: Harshad Reddy Nalla <[email protected]>
Signed-off-by: Harshad Reddy Nalla <[email protected]>
harshad16
force-pushed
the
virtualservice
branch
from
50b6026 to
a39f413
Compare
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.
related: #37
follow-up: #42
Descriptions:
The PR allow controller to connect each workspace with an endpoint that is reachable under the istio mesh.
This virtualservice follow the pattern of unqiue name, so it doesnt collide with notebook v1, if running in the same cluster parallely.
Setup:
The setup require to set the istio deployment in places.
for initial setup:
deploy istio using from kubeflow manifest repo
After deployment of istio, deploy the controller with the image from PR content
make deploy IMG=quay.io/harshad16/nbcv2:controller-istio2kubectl apply -k config/samples/Port forward the istio ingress:
Open the browser, and goto:
localhost:8080//workspace/<namespace>/<workspace-name>/jupyterlab/labCRD change with port in podtemplate:
#507
demo:
Screencast from 2025-07-28 16-43-01.webm