-
Notifications
You must be signed in to change notification settings - Fork 8k
Closed
Labels
area/networkinglifecycle/automatically-closedIndicates a PR or issue that has been closed automatically.Indicates a PR or issue that has been closed automatically.lifecycle/staleIndicates a PR or issue hasn't been manipulated by an Istio team member for a whileIndicates a PR or issue hasn't been manipulated by an Istio team member for a while
Description
Bug Description
Suppose there is a client, a vs and a service.
vs has port 8080 but routes to service on port 8081.
When the client defines a sidecar with egress listener depending on vs:8080, the service with port 8081 is not included in the sidecar scope, resulting in client proxy can not get the service configs. If client depends on vs:8081, it works. But I don't think it makes sense since vs does not have port 8081.
I think if client specify vs:8080, istio should be smart enough to pull in service on port 8081.
I believe the code to change is here, if it makes sense, happy to submit a fix.
Version
istio 1.12
Additional Information
No response
Metadata
Metadata
Assignees
Labels
area/networkinglifecycle/automatically-closedIndicates a PR or issue that has been closed automatically.Indicates a PR or issue that has been closed automatically.lifecycle/staleIndicates a PR or issue hasn't been manipulated by an Istio team member for a whileIndicates a PR or issue hasn't been manipulated by an Istio team member for a while