Kubernetes · Web Applications

Kubernetes Microservices

Ingress and Services routing to frontend and API Deployments inside a namespace. This diagram is written in ArchLex and passes Kubernetes provider checks.

Edit in the playground Kubernetes diagrams as code

Kubernetes Microservices: Ingress and Services routing to frontend and API Deployments inside a namespace

provider k8s
direction LR
validation normal

cluster production {
  namespace web {
    gateway: ingress
    frontend_service: service
    frontend: deployment
    api_service: service
    api: deployment

    gateway -[routes]-> frontend_service
    frontend_service -[targets]-> frontend
    frontend -[invokes]-> api_service
    api_service -[targets]-> api
  }
}

What is in this diagram.

Resources

gateway Ingress
frontend_service Service
frontend Deployment
api_service Service
api Deployment

Relationships

gateway routes frontend_service
frontend_service targets frontend
frontend invokes api_service
api_service targets api

Boundaries

cluster production
namespace web

Render it yourself.

Save the source as k8s-microservices.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.

npx @archlex/cli render k8s-microservices.arch --output k8s-microservices.svg

All examples