Handle multiple potentially overlapping wildcard ingress domains in istio. #9183
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.
How to categorize this PR?
/area networking
/area robustness
/kind enhancement
What this PR does / why we need it:
Handle multiple potentially overlapping wildcard ingress domains in istio.
With PR #9038, nginx was moved behind the istio ingress gateway. The same PR also enabled management of multiple ingress domains via the
Garden
resource.Unfortunately, istio is a bit picky about overlapping domains in certain scenarios. This could lead to failing reconciliation of the nginx-ingress managed resource.
Therefore, to prevent those situations this change splits the virtual services into separate instances per host so that istio does not complain and simply does the right thing.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
Release note: