Kubernetes 1.34 Cluster Deployment: Required Images & Roles (Core + Calico v3.27.0)

This reference guide enumerates every container image needed to deploy a Kubernetes 1.34 cluster with Calico v3.27.0 networking, explaining the purpose of each image to help operators verify completeness — especially in air-gapped environments.

Core Kubernetes 1.34 Component Images (7)

Control Plane Components

registry.k8s.io/kube-apiserver:v1.34.0

— Unified API entry point handling all client requests; implements authentication, authorization, and request validation; manages cluster state persistence via etcd. registry.k8s.io/kube-controller-manager:v1.34.0 — Runs the collection of controllers that handle node failure recovery, maintain desired Pod replica counts, and manage Service-to-Pod associations; continuously reconciles actual state with desired state. registry.k8s.io/kube-scheduler:v1.34.0 — Makes Pod scheduling decisions based on resource requirements, node affinity, and load; writes scheduling results to etcd via the API server for the target node's kubelet to execute. registry.k8s.io/etcd:3.6.4-0 — Distributed key-value store holding all cluster state data (Pod configs, Service definitions, node info, RBAC rules); provides strong consistency and high availability as the single source of truth.

Node Components

registry.k8s.io/kube-proxy:v1.34.0

— Network proxy running on every node; maintains iptables or IPVS rules to implement Service traffic forwarding for ClusterIP, NodePort, and LoadBalancer Service types. registry.k8s.io/pause:3.10.1 — The infra container for each Pod; holds the Pod's network namespace so all containers in the Pod share the same network stack; acts as the Pod lifecycle anchor for stability. registry.k8s.io/coredns/coredns:v1.12.1 — Built-in DNS service resolving Service names to ClusterIPs; supports the service-name.namespace.svc.cluster.local domain format.

Calico Network Plugin Images (Compatible with Kubernetes 1.34)

Recommended Calico version: v3.27.0. The following six images are required: quay.io/tigera/operator:v1.32.3 — Operator-based lifecycle manager for Calico; watches custom resources (Installation, FelixConfiguration) to automate deployment, configuration updates, and upgrades. quay.io/calico/cni:v3.27.0 — CNI plugin that allocates Pod IPs via Calico IPAM, configures virtual network interfaces, and sets up routing rules for Pod-to-Pod connectivity. quay.io/calico/node:v3.27.0 — DaemonSet-deployed per-node agent containing the Felix process; programs network policy rules, maintains cross-node routes, and reports health status. quay.io/calico/kube-controllers:v3.27.0 — Controller bundle synchronizing network policies, managing IP pools, and syncing Service endpoint information to ensure Calico resource consistency. quay.io/calico/typha:v3.27.0 — Performance optimizer for large clusters (>50 nodes); aggregates connections from multiple node agents to etcd, reducing etcd load and network traffic. quay.io/calico/pod2daemon-flexvol:v3.27.0 — FlexVolume driver that mounts node-level Calico configuration (certificates, policy rules) into Pods so in-Pod Calico components always have the latest config.

Version Matching Notes

All Kubernetes 1.34 core components must use the v1.34.0 tag (etcd, coredns, and pause versions as listed above).

Calico v3.27.0 with Operator v1.32.3 has validated compatibility with Kubernetes 1.34.

Verify required core image versions with kubeadm config images list.

Ensure every node's container runtime can pull or access all listed images (pre-load in offline environments).

For detailed compatibility matrices consult the official documentation:

Kubernetes: https://kubernetes.io/docs/ Calico:

https://docs.tigera.io/