Loading content
Kubernetes was originally developed by Google and is now the leading system for container orchestration. It allows developers to package applications in containers and run them in a distributed environment. Kubernetes provides features such as load balancing, self-healing, rollouts and rollbacks, as well as managing configurations and secrets.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Kubernetes is an open-source platform for orchestrating containerized applications through declarative state, scheduling, networking, and automated recovery.
Google released Kubernetes as an open-source project in 2014 and donated it to the Cloud Native Computing Foundation in 2015. It carried experience from Google cluster operations into an independent container ecosystem.
A Kubernetes cluster has a control plane that observes desired state and worker nodes that execute it. You describe Deployments, Services, and configuration; controllers continuously bring running reality back toward that description.
It combines control-plane and worker nodes for shared workloads.
It declares how many versions of an application should run.
It gives changing Pods a stable network endpoint.
Kubernetes is useful for running, releasing, and scaling containerized services reproducibly across machines. Teams still need explicit ownership for images, persistence, networking, security, and cost.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.