Help with Istio Internal Routing Configuration from external ingress controller #49860
Unanswered
assafsauer
asked this question in
Q&A
Replies: 1 comment
-
sovled by adding both hosts svc and external.. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on setting up an environment where Kong manages the external ingress for my applications, while Istio handles internal service-to-service communication. My understanding is that in this setup, Istio's Ingress Gateway might not be needed. Please correct me if this assumption is incorrect.
For testing purposes, I've attempted to create a routing rule that redirects traffic from an external domain (managed by Kong and pointing to python1) to python2 internally within the cluster. However, I've encountered an issue where the routing rule only works when using service names directly, but not with the external domain.
so this one being routed:
kubectl run curlpod --image=curlimages/curl --restart=Never --rm -it -- curl http://python1.python1.svc.cluster.local/greeting
this one failed:
curl -ks https://python1.apps.source-lab.io/greeting
many thanks!
Beta Was this translation helpful? Give feedback.
All reactions