Anthos service mesh

Google Cloud Serverless Applications
1

I installed anthos service mesh in a cluster using ‘asmcli’, show we enable Istio sidecar injection label on a namespace to view the deployments in ASM dashboard or will it work without labeling the namespace too

2

Hello ravichandra,

Automatic sidecar proxy injection (auto-injection) occurs when Anthos Service Mesh detects a namespace label you configure for the workload’s Pod. The proxy intercepts all inbound and outbound traffic to the workloads and communicates with Anthos Service Mesh. You can check the documentation for reference.

3

Thank you dionv. My problem is with Anthos service mesh.

I have both nginx and istio-proxy containers in my Workload’s pods. I enabled external access for few microservices in my GKE cluster using nginx’s ingress-nginx-controller. But I’m unable to monitor the traffic flowing through ingress-nginx-controller to my microservices.
In topology view I see there are no metrics data available to graph, and “ingress-nginx-controller” as an unknown service.
If I do the same using istio’s Ingress gateway, I’m able to monitor everything normally. May I know what can be the possible reasons for this?