<p>We have two Microservices A and B. A calls B through the istio-proxy side car.</p>
<p>We created a Virtual service. Please see below for the yaml</p>
<p>After creating the virtual service, when we check the routes in pod A using this command <code>istioctl proxy-config routes a-75768cc7bc-ghzsr -o json</code>, we do NOT see weighted routes</p>
<p>If we replace tls with http, weighted routes are added. Can we use weighted routes with tls ?</p>
<pre><code>apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: b
  namespace: default  
spec:
  hosts:
  - b
  tls:
  - match:
    - port: 443
    route:
    - destination:
        host: b
        subset: v1
      weight: 50
    - destination:
        host: b
        subset: v2
      weight: 50
</code></pre>
<p>Adding service definition</p>
<pre><code>apiVersion: v1
kind: Service
metadata:          
 labels:        
  svc: b
 name: b
 namespace: default      
spec:
  clusterIP: x.x.x.x
  ports:
  - name: https-b
    port: 443
    protocol: TCP
    targetPort: 8080
  selector:
    svc: b
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}
</code></pre>
<p>Adding Destination rule,</p>
<pre><code>apiVersion: networking.istio.io/v1beta1
kind: DestinationRule
metadata:  
  name: b
  namespace: default
spec:
  host: b
  subsets:
  - labels:
      version: v1
    name: v1
  - labels:
      version: v2
    name: v2
</code></pre>

<p>Is it possible that Service definition has port name with <code>http-service-a</code>?</p>
<p>From <a href="https://istio.io/latest/docs/reference/config/networking/virtual-service/#VirtualService" rel="nofollow noreferrer">VirtualService documentation</a>, HTTP and TLS have different spec.</p>
<p><code>http</code></p>
<blockquote>
<p>HTTP routes will be applied to platform service ports named ‘http-’/‘http2-’/‘grpc-*’, gateway ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service entry ports using HTTP/HTTP2/GRPC protocols.</p>
</blockquote>
<p><code>tls</code></p>
<blockquote>
<p>TLS routes will be applied to platform service ports named ‘https-’, ‘tls-’, unterminated gateway ports using HTTPS/TLS protocols (i.e. with “passthrough” TLS mode) and service entry ports using HTTPS/TLS protocols.</p>
</blockquote>
<p>Given the above difference, it could explain the different behaviour.</p>
<p>Which version of Istio are you using? It would be good to see K8s definitions as well.</p>
