Kubernetes microservices deployment with Istio Ingress Gateway routing traffic across three stateless services (svc-a, svc-b, svc-c) running on separate nodes, each scaled to three replicas via Deployments. Backend services communicate with Redis StatefulSet and SQL database StatefulSet in isolated namespaces, with persistent volumes securing data and Secrets managing credentials. This architecture demonstrates namespace isolation, service discovery via ClusterIP, stateful workload management, and secure credential handling—essential patterns for production Kubernetes clusters. Fork and customize this diagram on Diagrams.so to match your own microservices topology, node distribution, and storage requirements. The design separates ingress, application, and data tiers across dedicated nodes to optimize resource utilization and fault isolation.