grs
grs
That sounds then like istio is not honouring those annotations. I have no istio expertise I'm afraid. I would check the various env vars set on the istio side car...
From googling, some versions (or some istio installation methods) also require that traffic.sidecar.istio.io/includeInboundPorts: "*" by set explicitly, so could try that.
`kubectl exec -it -c istio-proxy -- bash` then `iptables --list` would I think give you the current redirect rules to verify that the annotations are not in effect
I would also change the console-auth setting for debugging purposes to eliminate the oauth-proxy container. What does kubectl/oc describe pod show?
traffic.sidecar.istio.io/excludeInboundPorts: 15090,15021 is wrong, and there appears to be no traffic.sidecar.istio.io/excludeOutboundPorts set. What about service-controller pod?
Also, stepping back, the 8888 port is only locally accessible when using oauth proxy, so actually we would not expect to be able to connect to that. There may be...
Try: `skupper init --annotations traffic.sidecar.istio.io/excludeInboundPorts='5671,5672,45671,55671,8081,8080' --annotations traffic.sidecar.istio.io/excludeOutboundPorts='5671,5672,45671,55671,8081'`
Try to curl 10.130.0.219:8080 from inside the namespace. There is no istio proxy sidecar on either pod in those details, but the annotations are at least as expected. I forgot...
That looks like it is working... what do you see for `skupper status`?
Try `curl https://10.130.0.219:8080` from inside the cluster. What do `oc get route` and `oc get svc` show?