Kubernetes

Kubernetes automates deployment, scaling, and management of containerized workloads across clusters of machines, using a declarative, desired-state model.

Containers & KubernetesOpen sourceSelf-hosted
Visit official website

Published Updated

CategoryContainers & Kubernetes
AccessSelf-hosted
PricingOpen source
APIAvailable
Overview

What is Kubernetes?

Kubernetes originated at Google, drawing on internal experience running containers at scale with systems like Borg, and was open-sourced in 2014. Google donated the project to the newly formed Cloud Native Computing Foundation (CNCF) in 2015, where it remains a graduated project governed independently of any single vendor.

Read the full overview

The system works by reconciling a declared desired state (which containers should run, how many replicas, what resources they need) against the cluster's actual state, restarting or rescheduling workloads as needed. It's extensible through Custom Resource Definitions (CRDs) and the operator pattern, which is how most third-party tools (service meshes, databases, CI/CD systems) integrate with it.

Sources checked 27 September 2026: Kubernetes concepts overview, architecture documentation.

Why teams use it

Key capabilities

  • Scheduling: Place containers onto cluster nodes based on declared resource requests.
  • Self-healing: Restart or reschedule failed containers to match desired state.
  • Service discovery and load balancing: Route traffic to healthy pods.
  • Extensibility: Add custom resources and controllers (operators) for domain-specific automation.
Core areas

Decide early whether you'll self-manage the control plane or use a managed Kubernetes service, since that changes upgrade and patching responsibility. Map networking (CNI plugin) and storage (CSI driver) choices before running production workloads.

Positioning

Kubernetes fits teams running enough containerized services that manual placement, scaling, and failover become impractical. Running it yourself means owning control-plane upgrades, networking (CNI), and storage (CSI) integration; most teams instead use a managed offering (EKS, GKE, AKS, or similar) and adopt vanilla Kubernetes concepts on top.

Why it matters

A useful evaluation deploys a real multi-service application, kills a pod and a node to confirm self-healing behavior, and checks whether the team's chosen networking and storage plugins meet actual production requirements.

Deployment & technical details

Technical details

Access
Self-hosted
Source model
Open source
Founded
2014
Headquarters
CNCF Project
Pricing model
Open source
Starting price
0 USD
API
Available
Published release
Kubernetes v1.37.1 ↗ (checked )
Source check
Primary source ↗ checked
Check with the publisher

Official resources

Before you shortlist

What to verify for your environment

Start from the users, systems and operating responsibilities the tool needs to support.

  • Confirm current features, licensing and support terms with the publisher.
  • Validate deployment, data location, access control, backup and recovery requirements.
  • Test integrations, export paths and a representative operational workflow before committing.
Community experience

Reviews of Kubernetes

Powerful but complex4/5 stars

Kubernetes solved our scaling and deployment challenges, but the learning curve is steep. It took our team several months to become proficient. Now that we have it running smoothly with ArgoCD for GitOps, it is incredibly powerful. Not recommended for small teams or simple applications though.

Alex R.

Loading review form…