Kubernetes Ingress to Service
This Kubernetes diagram traces a web request from the internet to an application. A load balancer receives HTTPS traffic and sends it to an ingress controller. The ingress controller applies a host rule and directs the request to a Kubernetes service. The service selects two web pod endpoints, which use a shared database. This picture helps distinguish ingress routing from service-to-pod routing. It is useful for explaining an application deployment to developers or reviewers. Add namespaces, network policies, or TLS certificates if those details change how traffic is handled. Keep the diagram current when equipment, cable paths, service ownership, or security boundaries change, so it remains useful for planning and operations.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Kubernetes application traffic
Key decisions
- External access: A load balancer receives HTTPS traffic.
- Routing: The ingress controller applies the host rule.
- Service discovery: The service forwards to pod endpoints.
When to reuse this
Use this to explain how public traffic reaches pods through Kubernetes ingress and a service.
Frequently asked questions
What is Kubernetes ingress?
What does a service do?
Why show more than one pod?
More kubernetes examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.