fix: handle multiple istio-ingress-route relations in jupyter-ui (backport #576)#577
Merged
Merged
Conversation
* fix: handle multiple istio-ingress-route relations in jupyter-ui * test: add multi-ingress integration test for jupyter-ui Deploy a second istio-ingress-k8s instance, relate it to jupyter-ui's istio-ingress-route endpoint, and assert the resulting HTTPRoute is created and attached to the second Gateway via parentRefs. Adjust concierge MetalLB CIDR to provide two IPs, one per Istio ingress gateway. * review: update unit and integration tests * review: add comment for ingress submit (cherry picked from commit 06cefb2)
NohaIhab
approved these changes
Jun 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Backport of #576 to
track/1.11.