istio: Waypoint -> Backend reports many `unknown` destination attributes for TCP services

istio_tcp_connections_opened_total{
    connection_security_policy="mutual_tls",
   destination_app="unknown",
   destination_canonical_revision="unknown",
   destination_canonical_service="unknown",
   destination_cluster="Kubernetes",
   destination_principal="unknown",
   destination_service="echo.default.svc.cluster.local",
   destination_service_name="echo",
   destination_service_namespace="default",
   destination_version="unknown",
   destination_workload="unknown",
   destination_workload_namespace="unknown",
   gateway_istio_io_managed="istio.io-mesh-controller",
   gateway_networking_k8s_io_gateway_name="waypoint",
   instance="10.244.0.36:15020",
   istio_io_dataplane_mode="none",
   job="kubernetes-pods",
   namespace="default",
   node="kind-control-plane",
   pod="waypoint-777578b889-8gmtt",
   pod_template_hash="777578b889",
   reporter="waypoint",
   request_protocol="tcp",
   response_flags="-",
   service_istio_io_canonical_name="waypoint",
   service_istio_io_canonical_revision="latest",
   sidecar_istio_io_inject="false",
   source_app="shell",
   source_canonical_revision="latest",
   source_canonical_service="shell",
   source_cluster="Kubernetes",
   source_principal="spiffe://cluster.local/ns/default/sa/default",
   source_version="latest",
   source_workload="shell",
   source_workload_namespace="default"
}

Lots of unknowns – they should not be!

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 16 (15 by maintainers)

Most upvoted comments

Ill try other versions. I think this suggests we are not getting the peer metadata though