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.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response