I feel like I’m missing something important, and was hoping for some clarification.
Under a normal kubernetes architecture, a microservice will send traffic to another microservice via the kubernetes
service resource. i.e., the
service will identify which pod(s) to send traffic to based on the label selectors & health of the pods.
When there is istio in the mix… Is that still the case? The points of confusion for me are:
DestinationRulesaffect where traffic from
VirtualServicesare sent - i.e. the traffic needs to hit the
VirtualServiceis set up to inspect traffic from a
Gateway, and then to route the traffic to kubernetes services based on route prefixes, or headers (etc) - and
DestinationRules further refine that.
Gatewayis used essentially to expose host names (
api.example.org) & act as a reverse proxy for external traffic
So does that mean that in an Istio enriched cluster, my microservices need to use the external host name to gain the benefit for the
DestinationRule? That doesn’t seem right… Is there still a way for me to send requests to the kubernetes
service and still benefit from the
Thank you in advance!