hello,
we have kong ingress as our ingress controller on our aws eks cluster, and kuma as our service mesh.
whenever we intercept or teleport a deployment, we can't access the service from outside, only from the inside. so the internal routes work well but the external don't work. it is relevant to both the original service and the intercepted one as well.
we have kuma sidecar added to each pod in the namespace, your intercepted pod gets it as well.
hello, we have kong ingress as our ingress controller on our aws eks cluster, and kuma as our service mesh. whenever we intercept or teleport a deployment, we can't access the service from outside, only from the inside. so the internal routes work well but the external don't work. it is relevant to both the original service and the intercepted one as well. we have kuma sidecar added to each pod in the namespace, your intercepted pod gets it as well.
what can we do?
@c6o/cli/1.1.1 darwin-x64 node-v14.17.3