Skip to content

fix: handle multiple istio-ingress-route relations (backport #214) - #215

Merged
NohaIhab merged 1 commit into
track/2.4from
backport-214-to-track/2.4
Jun 24, 2026
Merged

NohaIhab merged 1 commit into
track/2.4from
backport-214-to-track/2.4

Conversation

@ckfbot

@ckfbot ckfbot commented Jun 23, 2026

Copy link
Copy Markdown

Description

Backport of #214 to track/2.4.

* fix: handle multiple istio-ingress-route relations

Use model.relations[...] (a list) instead of model.get_relation(...) when
checking ambient vs. sidecar ingress, so envoy no longer raises
TooManyRelatedAppsError when more than one istio-ingress-route relation is
present.

Add unit and integration coverage for multiple ambient ingress relations
and widen the metallb CIDR so the integration tests can deploy a second
Istio ingress gateway.

* test: strengthen istio-ingress-route unit tests

Assert every istio-ingress-route relation receives a valid HTTPRoute config.

* test: verify web-grpc mlmd access before and after second ingress

(cherry picked from commit c88457d)
@NohaIhab
NohaIhab merged commit 1c11b1e into track/2.4 Jun 24, 2026
12 checks passed
@NohaIhab
NohaIhab deleted the backport-214-to-track/2.4 branch June 24, 2026 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants