One of the ways a service mesh can actually make it more complicated to manage a Kubernetes environment is when it must be configured separately from the Ingress controller. Separate configurations aren’t just time‑consuming, either. They increase the probability of configuration errors that can prevent proper traffic routing and even lead to security vulnerabilities (like bad actors gaining access to restricted apps) and poor experiences (like customers not being able to access apps they’re authorized for). Beyond the time it takes to perform separate configurations, you end up spending more time troubleshooting errors.
You can avoid these problems – and save time – by integrating NGINX Plus Ingress Controller with NGINX Service Mesh to control both ingress and egress mTLS traffic. In this video demo, we cover the complete steps.
Supporting documentation is referenced in the following sections:
Before starting the actual demo, we performed these prerequisites:
bookinfoapp, inject the NGINX Service Mesh sidecar, and deploy the app.
#blog #tech #microservices #service mesh