advancedService Mesh: Istio, Envoy & mTLS
After enabling STRICT mTLS mesh-wide, a legacy monitoring agent starts failing to scrape application endpoints
The monitoring agent is not in the mesh (no sidecar) so it sends plaintext traffic. STRICT mode rejects plaintext connections. Fix: enroll the monitoring namespace in the mesh, or create a PeerAuthentication exception for that specific port/workload, or switch to permissive mode for that namespace.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.
After enabling STRICT mTLS mesh-wide, a legacy monitoring agent starts failing to scrape application endpoints