Quite new to Istio, Kubernetes. These question are very much Kubernetes + Istio centric.
Are Istio VirtualService instances part of the Istio Service Registry such that VirtualService A can route traffic to VirtualService B via A’s spec.http.route.destination.host: B.name ? Or are destination.host values limited to Kubernetes service entities? Is there a CLI mechanism to determine what the Service Registry contains? Great concept but being able to view ‘contents’ pretty useful too I don’t see any mention of any of my defined VirtualServices in the istioctl proxy-config route pod -o json for the Pods in my mesh, except for metadata.filterMetadata.istio.config paths (eg. “config”: “/apis/networking/v1alpha3/namespaces/default/virtual-service/mms-elastic-debug-vs”). In the same output, I do see plenty of references to expected K8S DNS entries (eg. alfresco.default.svc.cluster.local)
Am I wrong in my understanding that once a VirtualService routes via a k8s Service instance, that Service instance can only make use of a Deployment/Pod via the Service’s selector? To chain VirtualServices, k8s Services must be kept out of the chain? And therefore, my earlier question about VirtualService being a route destination.
Just looking to flush out my understanding so I don’t go down the wrong path, mesh topology speaking.