New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test framework .Call fails due to port mismatch #13091
Comments
I think we can just remove the check, unless there is some context I am missing why we have it |
@howardjohn I think this should be resolved in #13175. The echo component has been re-written to support both native and kube. It also has the separation of servicePort and instancePort (i.e. TargetPort). Would you mind trying it out and confirming? |
@howardjohn did you get a chance to look at @nmittler's recommendation? |
Was using the service port, but should have been using the target port. Fixes istio#13091
I think this should fix it: #13443 |
Fixed |
@howardjohn what PR fixed this? |
This fails with:
I think this is because we have:
in the Service.
https://github.com/istio/istio/blob/master/pkg/test/framework/components/apps/kube.go#L619-L621
The text was updated successfully, but these errors were encountered: