This article draws on source material originally published at enterprisersproject.com. Quotes and attributions are preserved from that source.
What Is Kubernetes?
Kubernetes — often abbreviated as k8s (k, eight characters, s) or simply called kube — is an open source platform that automates the deployment, scaling, and operation of containerized applications. The name comes from the Greek word for “helmsman” or “sailing master,” a fitting metaphor for a system that steers fleets of containers through complex production environments.
Red Hat technology evangelist Gordon Haff and Senior Distinguished Engineer William Henry offer a concise definition in their book From Software and Vats to Programs and Apps:
“Kubernetes eliminates many of the manual processes involved in deploying and scaling containerized applications. In other words, you can cluster together groups of hosts running Linux containers, and Kubernetes helps you easily and efficiently manage those clusters.”
Gordon Haff & William Henry, Red Hat
Dan Kohn, former executive director of the Cloud Native Computing Foundation (CNCF), put it in broader context:
“Containerization is this trend that’s taking over the world to allow people to run all kinds of different applications in a variety of different environments. When they do that, they need an orchestration solution in order to keep track of all of those containers and schedule them and orchestrate them. Kubernetes is an increasingly popular way to do that.”
Dan Kohn, Cloud Native Computing Foundation
What Is Kubernetes Used For?
Containers appeal to organisations across a wide range of workloads. But running containers at scale — especially in conjunction with microservices — demands careful planning and robust tooling. For stateful applications such as databases, the operational complexity is even greater. That is precisely where Kubernetes earns its place.
In organisations practising DevOps — short sprints, experimentation, rapid iteration — containers have become central to how software is built and delivered. Kubernetes provides the orchestration layer that makes container-based workflows reliable and repeatable in production.
Ashesh Badani, SVP and General Manager for Cloud Platforms at Red Hat, summarises the opportunity:
“Once organisations understand the benefits of containers and Kubernetes for DevOps, application development, and delivery, it opens up so many possibilities, from modernising traditional applications, to hybrid- and multi-cloud implementations and the development of new, cloud-native applications with speed and agility.”
Ashesh Badani, Red Hat
For a more concrete mental model, Mike Kail, CTO and co-founder at CYBRIC, offers a lunchbox analogy:
“Let’s say an application environment is your old-school lunchbox. The contents of the lunchbox were all assembled well before putting them into the lunchbox — there was no isolation between any of those contents. The Kubernetes system provides a lunchbox that allows for just-in-time expansion of the contents (scaling) and full isolation between every unique item in the lunchbox and the ability to remove any item without affecting any of the other contents (immutability).”
Mike Kail, CYBRIC
Why Use Kubernetes?
Kubernetes lets you schedule and run containers on clusters of physical or virtual machines while automating a substantial range of operational tasks. As container adoption grows within an organisation, the value of having an orchestration layer — rather than managing each container manually — compounds quickly.
Sean Suchter, co-founder and CTO of Pepperdata, illustrates what life without orchestration looks like:
“Without an orchestration framework of some sort, you’ve just got services running ‘somewhere’ — where you set them to run, manually — and if you lose a node or something crashes, it’s manual work to fix it. With an orchestration framework, you declare how you want your environment to look, and the framework makes it look like that.”
Sean Suchter, Pepperdata
The core value proposition of Kubernetes can be summarised in three points:
- Automation: Kubernetes handles scheduling, self-healing (restarting failed containers), and rolling updates without manual intervention.
- Scalability: Workloads can be scaled up or down declaratively, and Kubernetes will reconcile the actual state of the cluster with the desired state.
- Portability: Kubernetes runs on public clouds, private data centres, and hybrid environments, reducing vendor lock-in.
Badani adds that Kubernetes occupies a rare position in enterprise technology:
“Kubernetes is one of those rare technologies that appeals to developers, operations teams, and lines of business. It’s a win-win-win situation that offers benefits to all constituents in terms of productivity, collaboration, and meeting the needs of customers.”
Ashesh Badani, Red Hat
What Kubernetes Does: The Broader Ecosystem
Kubernetes is a critical piece of the cloud-native puzzle, but it does not operate in isolation. Haff notes that the real power of the cloud-native ecosystem comes from the complementary projects that surround Kubernetes:
- Service meshes: Istio for traffic management and observability between services
- Monitoring: Prometheus for metrics collection and alerting
- Container tooling: Podman as a daemonless container engine
- Distributed tracing: Jaeger and Kiali for understanding request flows across microservices
- Container registries: Quay as an enterprise-grade registry
- Image inspection: Skopeo for working with container images without running them
- Foundation: Linux, which underpins all the containers that Kubernetes orchestrates
Enterprise platforms such as Red Hat OpenShift bundle many of these integrations, reducing the time teams spend selecting and wiring together individual tools.
Key Kubernetes Trends
1. The Rise of Kubernetes-Native Software
Josh Komoroske, senior DevOps engineer at StackRox, identifies a meaningful shift in how software is being designed. Early Kubernetes adoption was characterised by the realisation that existing software could be containerised and managed with Kubernetes. The next wave is software built explicitly for Kubernetes from the start:
“Think not only containerised software that happens to be deployable in Kubernetes, but also software that is aware of and able to provide unique value when deployed in Kubernetes. Software that is released and branded as ‘Kubernetes-first’ will be increasingly common, possibly manifesting as custom resource definitions or Kubernetes Operators.”
Josh Komoroske, StackRox
2. Security as a First-Class Concern
As Kubernetes deployments move from experimental to mission-critical, security risk exposure grows proportionally. Rani Osnat, VP of Strategy at Aqua Security, explains:
“As the adoption of Kubernetes and deployment of container-based applications in production accelerate to much higher volumes than we’ve seen to date, we can expect more security incidents to occur. Most of those will be caused by the knowledge gap around what constitutes secure configuration, and lack of proper security tooling.”
Rani Osnat, Aqua Security
This does not reflect inherent flaws in Kubernetes itself — the community has a visible commitment to security — but rather the reality that new deployment patterns bring new attack surfaces that operators must understand and mitigate.
3. Other Emerging Trends
- Federation: Managing workloads across multiple Kubernetes clusters
- Talent demand: Growing competition for engineers with Kubernetes expertise
- Resource efficiency: Ongoing efforts to reduce the resource overhead of Kubernetes itself
Core Kubernetes Concepts Defined
What Is a Kubernetes Cluster?
A cluster is the foundational unit of a Kubernetes deployment: a group of nodes that collectively run your containerised applications. You interact with and manage the cluster — and therefore your applications — through Kubernetes.
What Is a Kubernetes Node?
A node is an individual physical or virtual machine within a cluster. Each node is a “worker” machine that runs the container runtime and other services necessary to execute your application containers. Kubernetes manages and monitors nodes, redistributing workloads if a node becomes unhealthy.
What Is a Kubernetes Pod?
A pod is the smallest deployable object in Kubernetes. It represents one or more containers that are scheduled and run together on a node, sharing network namespace and storage. Containers within a pod communicate with each other via localhost. Pods are ephemeral: Kubernetes creates and destroys them as needed to maintain your declared application state.
What Is a Kubernetes Operator?
Kubernetes excels at managing stateless applications. For stateful applications — databases, message queues, and similar workloads — operational tasks such as provisioning, scaling, backup, and failover require domain-specific knowledge that cannot be captured by generic Kubernetes primitives alone.
Jeremy Thompson, CTO at Solodev, describes the challenge:
“Adding or removing instances may require preparation and/or post-provisioning steps — for instance, changes to its internal configuration, communication with a clustering mechanism, interaction with external systems like DNS, and so forth. Historically, this often required manual intervention, increasing the DevOps burden and increasing the likelihood of error.”
Jeremy Thompson, Solodev
The solution is the Operator pattern, introduced by CoreOS in 2016. An Operator is a Kubernetes controller that encodes the operational knowledge of a specific application — think of it as a “robot sysadmin” for that application, built using the Kubernetes API.
Matthew Dresden, director of DevOps at Nexient, explains the mechanism:
“Operators are clients of the Kubernetes API that control custom resources. This capability enables automation of tasks like deployments, backups, and upgrades by watching events without editing Kubernetes code.”
Matthew Dresden, Nexient
The Operator Framework, launched in March 2018, provided a structured SDK for building and packaging Operators. The community registry OperatorHub.io — launched by Red Hat in conjunction with Amazon, Microsoft, and Google — is a central location for discovering and sharing Operators.
Liz Rice, VP of Open Source Engineering at Aqua Security and CNCF Technical Oversight Committee chair, describes the growth:
“At the CNCF, we’re seeing interest in projects related to managing and discovering Kubernetes Operators, as well as observing an explosion in the number of Operators being implemented. Project maintainers and vendors are building Operators to make it easier for people to use their projects or products within a Kubernetes deployment.”
Liz Rice, Aqua Security / CNCF
What Is a Kubernetes Secret?
A Secret is a Kubernetes object designed to store sensitive data — such as passwords, OAuth tokens, or SSH keys — separately from application code and pod definitions. Secrets can be mounted into pods at runtime, making the sensitive data available to the application without embedding it in a container image or pod spec.
As the official Kubernetes documentation states: “Putting this information in a Secret is safer and more flexible than putting it verbatim in a Pod definition or in a container image.”
Secrets embody a form of the least-privilege principle: your application gets exactly the credentials it needs at runtime, without granting blanket access to sensitive data across the cluster.
What Is kubectl?
kubectl (note the lowercase k — this is the official style) is the command-line interface for interacting with Kubernetes clusters. It communicates with the Kubernetes API server and follows a consistent command structure:
kubectl [command] [TYPE] [NAME] [flags]Code language: CSS (css)Common commands include:
kubectl get pods— list running pods in the current namespacekubectl apply -f manifest.yaml— apply a configuration from a YAML filekubectl describe pod <name>— show detailed information about a podkubectl logs <pod-name>— retrieve logs from a containerkubectl delete pod <name>— delete a specific pod
What Is Minikube?
Minikube is an open source tool that runs a single-node Kubernetes cluster inside a virtual machine on your local workstation. It supports Linux, macOS, and Windows and is designed for development, learning, and local testing — not production use.
Chris Ciborowski, CEO and co-founder at Nebulaworks, highlights its accessibility:
“With just a few installation commands, anyone can have a fully functioning Kubernetes cluster, ready for learning or supporting development efforts.”
Chris Ciborowski, Nebulaworks
To get started, you will need to install both Minikube and kubectl. The official Kubernetes documentation provides installation guides and a quickstart for both tools. Note that Minikube is a single-node cluster and does not replicate the behaviour of multi-node production clusters in areas such as scheduling and network policy.
Summary
Kubernetes has become the de facto standard for container orchestration because it addresses real operational problems — manual scaling, fragile deployments, and the complexity of managing large numbers of containers — with a declarative, extensible, and community-backed platform. Understanding its core primitives (clusters, nodes, pods, Secrets), its extension model (Operators), and its tooling (kubectl, Minikube) is an essential foundation for any DevOps engineer working in a containerised environment.
As adoption matures, the focus is shifting from “can we use Kubernetes?” to “how do we use Kubernetes securely, efficiently, and as a first-class design target for new software?” Those are the questions that will define Kubernetes practice for the foreseeable future.