Kubernetes Multi-Namespace App Diagram

Kubernetes Multi-Namespace Application

This Kubernetes application diagram groups frontend and backend resources into namespaces. An ingress controller receives public HTTPS traffic and routes it to a web service in the frontend namespace. The service selects web pods, which call an API service in the backend namespace. That service selects API pods, and only the API pods connect to PostgreSQL. The view is useful for documenting ownership and traffic boundaries in a microservices deployment. Add network policies, secrets, queues, or separate databases when they are important to the application design. 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 application with an ingress controller, a frontend namespace containing a web service and web pods, and a backend namespace containing an API service, API pods, and PostgreSQL; web pods call the API.”

接著試試Add a network policy between the namespacesAdd a worker service in the backend namespace

這張圖裡有什麼

看懂背後的決策。

01Separation

Frontend and backend resources use separate namespaces.

02Routing

Ingress reaches the frontend service.

03Data access

API pods are the only application tier connected to PostgreSQL.

Use this to show namespace boundaries and calls across a two-tier Kubernetes application.

瀏覽所有網路圖範本 →

常見問題

What is a Kubernetes namespace?

A namespace is a logical grouping for resources within a Kubernetes cluster.

Can services communicate across namespaces?

Yes, services can be addressed across namespaces when networking permits it.

Why separate frontend and backend?

Separate namespaces make ownership, permissions, and policy boundaries clearer.