Study guide

5.1 Kubernetes Distributions, Installation Tools & Managed Services

Kubernetes and Cloud Native Associate KCNA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the KCNA Exam & Certification Path 1.2 How to Use This Study Guide

2 Chapter 2: Kubernetes Fundamentals - Cluster Architecture & the API

2.1 Kubernetes Architecture & Control Plane Components 2.2 Worker Node Architecture & Node Components 2.3 Kubernetes API, Declarative Management & kubectl 2.4 Kubernetes Releases, API Versioning & Deprecation Policy

3 Chapter 3: Kubernetes Fundamentals - Workloads & Configuration

3.1 Core Workload Objects (Pods, Deployments & ReplicaSets) 3.2 Advanced Controllers (StatefulSets, DaemonSets, Jobs & CronJobs) 3.3 Namespaces, Labels, Selectors & Annotations 3.4 ConfigMaps, Secrets & Application Configuration 3.5 Pod & Container Lifecycle, Restart Policies & Graceful Termination

4 Chapter 4: Kubernetes Fundamentals - Scheduling & Autoscaling

4.1 Scheduling, Resource Management & Node Selection 4.2 Advanced Scheduling: Affinity, Topology Spread, Priority & Disruption Budgets 4.3 Autoscaling Workloads & Clusters (HPA, VPA, Cluster Autoscaler, KEDA)

5 Chapter 5: Kubernetes Fundamentals - Cluster Administration & Extensibility

5.1 Kubernetes Distributions, Installation Tools & Managed Services 5.2 Cluster Administration: Node Maintenance, Upgrades & etcd Backup 5.3 Extending Kubernetes: CRDs, Operators & the Controller Pattern

6 Chapter 6: Kubernetes Fundamentals - Containerization

6.1 Container Fundamentals, Runtimes & Registries 6.2 Container Image Anatomy: Layers, Tags, Digests & Pull Policy

7 Chapter 7: Container Orchestration - Networking & Service Discovery

7.1 Kubernetes Networking, Services & Ingress 7.2 Cluster DNS & Service Discovery with CoreDNS 7.3 NetworkPolicies, Zero-Trust Segmentation & the Gateway API

8 Chapter 8: Container Orchestration - Storage

8.1 Storage Concepts (PVs, PVCs, StorageClasses & CSI) 8.2 Volume Types, Snapshots & Stateful Storage Operations

9 Chapter 9: Container Orchestration - Security

9.1 Kubernetes Security & Access Control (RBAC & ServiceAccounts) 9.2 The 4C's of Cloud Native Security & Supply-Chain Trust 9.3 Service Mesh, mTLS & Zero-Trust Service Identity

10 Chapter 10: Container Orchestration - Troubleshooting

10.1 Container Troubleshooting & Health Probes 10.2 Cluster & Node-Level Troubleshooting

11 Chapter 11: Cloud Native Application Delivery

11.1 Cloud Native CI/CD Pipelines & Build Tooling 11.2 GitOps & Package Management (Helm, Kustomize, Argo CD & Flux) 11.3 Deployment Strategies & Release Management 11.4 Progressive Delivery Automation: Argo Rollouts, Flagger & Feature Flags 11.5 Application Debugging & Developer Workflows in Kubernetes 11.6 Platform Engineering & Developer Self-Service

12 Chapter 12: Cloud Native Architecture - Observability & Principles

12.1 Cloud Native Observability (Logging, Metrics & Tracing) 12.2 Cloud Native Principles & Architecture Patterns 12.3 Serverless, FaaS & Event-Driven Architecture

13 Chapter 13: Cloud Native Architecture - CNCF Ecosystem & Community

13.1 The CNCF Landscape, Governance & Project Lifecycle 13.2 Cloud Native Community, Collaboration & Contribution

5.1 Kubernetes Distributions, Installation Tools & Managed Services

Key Takeaways Explain This Topic AI

The CNCF Certified Kubernetes Conformance Program is what allows any conformant distribution to run the same manifests, and it is the reason vendors may use the Kubernetes trademark.

minikube, kind, and k3d create throwaway local clusters for development; kind runs Kubernetes nodes as Docker containers and is widely used in CI.

kubeadm is the upstream tool for bootstrapping a production-grade self-managed cluster; it configures the control plane but deliberately does not install a CNI plugin.

Managed services such as EKS, GKE, and AKS run and upgrade the control plane for you, so the shared responsibility line falls between the control plane and the worker nodes.

K3s and MicroK8s are lightweight conformant distributions aimed at edge, IoT, and constrained environments where a full control plane is too heavy.

Last updated: August 2026

5.1 Kubernetes Distributions, Installation Tools & Managed Services

Quick Answer: Kubernetes is upstream source code, not a product you install. You obtain a cluster either by building one ( kubeadm , kubespray , Cluster API ), by running a distribution (K3s, MicroK8s, OpenShift, Rancher), by spinning up a local sandbox (minikube, kind, k3d), or by renting a managed control plane (EKS, GKE, AKS). The CNCF Certified Kubernetes Conformance Program is what guarantees your manifests behave the same on all of them.

KCNA asks this from the platform-literacy angle: given a scenario — a laptop demo, an edge site, a regulated data centre, a startup with no platform team — which option fits, and who is responsible for what?

1. Certified Kubernetes Conformance

Before the options, the standard that unites them. The CNCF Certified Kubernetes Conformance Program runs an open-source test suite ( Sonobuoy executes the upstream conformance tests) against a candidate platform. Passing means:

All required Kubernetes APIs are present and behave as specified.

No proprietary API has been substituted for a standard one.

The vendor may use the Kubernetes trademark and the "Certified Kubernetes" mark.

Certification is per minor version , and vendors must recertify to stay listed.

This programme is the practical meaning of "no vendor lock-in" in the cloud native world: a Deployment written against GKE applies unchanged to OpenShift or K3s. Over 100 vendors maintain certified offerings.

2. Local and Development Clusters

Tool How it works Best for

minikube Runs a single-node (optionally multi-node) cluster in a VM or container driver. Rich add-on catalogue: Ingress, dashboard, registry, metrics-server. Learning, demos, feature exploration

kind (Kubernetes IN Docker) Runs each Kubernetes node as a Docker container . Extremely fast to create and destroy. CI pipelines, testing operators, multi-node simulation

k3d Runs K3s nodes in Docker containers. Very low memory footprint. Lightweight local multi-cluster work

Docker Desktop / Rancher Desktop A one-checkbox single-node cluster bundled with the desktop container runtime. Quick start with zero configuration

None of these are production tools — a single-node cluster has no failure domain, no HA control plane, and no real storage.

  • 3. Building a Self-Managed Cluster
  • kubeadm

kubeadm is the upstream, officially supported way to bootstrap a conformant cluster. It generates certificates, writes the control plane as static Pods into /etc/kubernetes/manifests , configures kubelet, and issues join tokens for worker nodes. # On the first control plane node

kubeadm init --pod-network-cidr=10.244.0.0/16

  • # On each worker
  • kubeadm join 10.0.0.10:6443 --token <token> \
  • -discovery-token-ca-cert-hash sha256:<hash>

What kubeadm deliberately does not do is a favourite exam point: it does not install a CNI plugin . Immediately after kubeadm init , nodes report NotReady and CoreDNS sits Pending , because there is no Pod network. You must apply Calico, Cilium, Flannel, or another CNI yourself. kubeadm also does not install an Ingress controller, a storage driver, or a monitoring stack — it deliberately stops at a minimum viable cluster.

Other Build Paths

kubespray — Ansible playbooks that install and manage production clusters across bare metal and clouds.

Cluster API (CAPI) — a CNCF project that manages clusters as Kubernetes objects , so a management cluster declaratively provisions and upgrades workload clusters. This is the modern GitOps-friendly answer to fleet management.

kOps — an opinionated tool for building and maintaining production clusters, historically strongest on AWS.

4. Lightweight and Edge Distributions

Distribution Notes

K3s (from Rancher/SUSE, donated to the CNCF) A single binary under 100 MB. Replaces etcd with embedded SQLite by default and strips legacy and cloud-provider code. Fully conformant. Targets edge, IoT, ARM, and CI.

MicroK8s (Canonical) Snap-packaged, single-command install, add-on driven; popular on Ubuntu and appliances.

K0s Single-binary distribution with a similar zero-dependency philosophy.

These matter for KCNA because the exam frames cloud native as spanning public, private, hybrid, and edge environments — a full control plane is not viable on a retail store's gateway device.

5. Enterprise Distributions

Red Hat OpenShift , SUSE Rancher , VMware Tanzu , and Mirantis Kubernetes Engine package upstream Kubernetes with an opinionated set of additions: an integrated registry, a build system, developer consoles, hardened security defaults (OpenShift enforces non-root containers via SecurityContextConstraints), multi-cluster management, and commercial support. They are conformant, so standard manifests work — but they add proprietary CRDs ( Route , BuildConfig , DeploymentConfig ) that do not exist elsewhere.

6. Managed Kubernetes and Shared Responsibility

Amazon EKS , Google GKE , Azure AKS , and their peers run the control plane as a service. The single most important idea is the responsibility split : ┌───────────────────────────────────────────────────────────┐

  • │ CLOUD PROVIDER OWNS │
  • │ • kube-apiserver, etcd (backup, HA, patching) │
  • │ • kube-scheduler, kube-controller-manager │
  • │ • control plane availability SLA and version upgrades │
  • ├───────────────────────────────────────────────────────────┤
  • │ YOU OWN │
  • │ • worker node pools, node OS patching, node autoscaling │
  • │ • workloads, RBAC, NetworkPolicies, Secrets hygiene │
  • │ • deciding when to trigger node upgrades │
  • │ • cost, quotas, and the add-ons you install │
  • └───────────────────────────────────────────────────────────┘

Managed offerings usually also provide a serverless node option (EKS Fargate, GKE Autopilot, AKS virtual nodes) that removes worker-node management as well, at a higher per-Pod price and with tighter constraints on privileged workloads and DaemonSets.

7. Choosing

  • Scenario Sensible choice
  • Learning on a laptop minikube or kind
  • Ephemeral cluster in a CI job kind
  • Air-gapped bare metal, must control everything kubeadm or kubespray
  • Hundreds of retail edge sites K3s
  • Small team, no platform engineers, already on a cloud Managed EKS/GKE/AKS
  • Regulated enterprise wanting vendor support OpenShift or Rancher
  • Managing a fleet of clusters declaratively Cluster API