Skip to content
Cards for the control plane, worker nodes, ingress controller, service and monitoring laid over a photo of a stack of server racks.

Kubernetes Cluster Architecture

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

An HTTPS request from a client reaches the ingress controller, which terminates TLS and routes by host and path to a ClusterIP Service. Kube-proxy rules on each worker node spread that traffic across the app pods. Control traffic follows a separate path. Each kubelet reports node and pod status to the API server, which is the only component that reads and writes etcd. The scheduler places new pods on nodes, and the controller manager keeps replica counts at the desired level.

Losing etcd quorum stops all cluster changes, but pods that are already running keep serving traffic, so the data plane survives a control plane outage. The design runs etcd with three or five members across zones, encrypted at rest. Network policies restrict pod-to-pod traffic, because the network plugin only gives pods their addresses. A team that wants a different stack can pick its own ingress controller and monitoring tools and keep the request and control paths as drawn.

Useful for

  • Designing a self-managed Kubernetes cluster for a production web app
  • Explaining control plane and node roles to a new platform team
  • Planning etcd backups and quorum for a multi-zone cluster

What's included

  • A designed cover slide
  • The diagram: 14 components and 9 connections as editable shapes
  • A components table and the 7-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename Clients, Ingress controller, Service (ClusterIP) and the other boxes inside Kubernetes cluster (production) to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 7-step data flow and the 8-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download kubernetes-cluster-architecture-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

Why does etcd need three or five members?

etcd decides changes by majority quorum, so an odd number is used. Three members tolerate one failure and five tolerate two. Spreading members across zones keeps the quorum alive when one zone fails.

What happens to running pods if the control plane goes down?

Pods that are already running keep serving traffic, because the kubelet and kube-proxy on each node keep their current state. What stops is change: no new pods are scheduled and no objects are created or updated until the API server and etcd return.

What is the difference between a Service and an Ingress?

A Service gives a stable virtual IP and DNS name for a set of pods inside the cluster. An Ingress routes outside HTTP and HTTPS requests by host and path to Services, and an ingress controller carries out those rules.

  • #infrastructure-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

More infrastructure diagram templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…