Kubernetes Ingress and Service Diagram

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.

類型 網路圖標準 Cisco-convention topology icons引擎 schematex-network更新時間 2026/9/24

需求

“A Kubernetes web application: internet users reach a load balancer, then an ingress controller with a host rule, a web service, two web pods, and a shared database.”

接著試試Add TLS termination at the ingress controllerAdd a second service for an API path

這張圖裡有什麼

看懂背後的決策。

01External access

A load balancer receives HTTPS traffic.

02Routing

The ingress controller applies the host rule.

03Service discovery

The service forwards to pod endpoints.

Use this to explain how public traffic reaches pods through Kubernetes ingress and a service.

瀏覽所有網路圖範本 →

常見問題

What is Kubernetes ingress?

Ingress defines how external HTTP or HTTPS traffic is routed to services.

What does a service do?

A service provides a stable endpoint and directs traffic to matching pods.

Why show more than one pod?

Multiple pods illustrate that a service can distribute requests across endpoints.