---
title: "Kubernetes | Skills We Assign For | Azendo"
description: "Kubernetes as an operating platform — when the complexity is justified, when it is not, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/kubernetes/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# Kubernetes.

Kubernetes is an orchestration platform that runs containerised applications across a cluster of machines, handling scheduling, restarts, scaling and networking. It is infrastructure for running software, not a framework for writing it.

## Where Kubernetes fits on a long engagement.

Kubernetes solves a real problem once you have enough services that placing them by hand stops being reasonable. It gives every team the same deployment interface, recovers from a failed node without anyone waking up, and makes scaling a configuration change rather than a project.

It is also the clearest example of a platform adopted before it was needed. Three services on two machines do not need a cluster; they need a deploy script and a backup. Kubernetes introduces its own class of incident — misconfigured limits, evictions, networking that behaves differently in production — and those need an owner who is not also the product team.

## What an assigned team does with Kubernetes.

A cluster needs an owner who is not also shipping features, because the two jobs interrupt each other and the platform always loses. Organisations that adopt Kubernetes without that person get a cluster configured once, upgraded never, and understood by whoever happens to be on call.

The work is continuous by nature — version upgrades, certificate rotation, capacity, the incident that turns out to be a memory limit set in 2023\. That is assigned under [DevOps managed services](https://azendo.co/services/cloud-and-devops/) rather than as a migration project with an end date.

## What we use Kubernetes for.

* One deployment path for several teams Teams shipping without each inventing their own release process, which is where platform engineering earns its cost.
* Making scale a setting rather than a project Capacity that follows demand, with limits set from measured behaviour rather than guessed at.
* Taking the cluster off the product team Someone owning the platform so feature engineers stop losing days to it.

## How Kubernetes capacity is assigned.

Cluster work is assigned under DevOps as a service, inside your own cloud account. Where the honest answer is that you do not need Kubernetes yet, we will say that at scoping. Capacity is agreed as a [committed monthly capacity](https://azendo.co/pricing/) rather than per skill.

## Roles we assign Kubernetes for

* [DevOps Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/devops-engineer/)
* [Platform Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/platform-engineer/)
* [Site Reliability Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/site-reliability-engineer/)
* [ML Platform Engineer MLOps engineering](https://azendo.co/services/mlops-engineering/ml-platform-engineer/)
* [MLOps Engineer MLOps engineering](https://azendo.co/services/mlops-engineering/mlops-engineer/)
* [Model Deployment Engineer MLOps engineering](https://azendo.co/services/mlops-engineering/model-deployment-engineer/)
* [Software Architect Software development](https://azendo.co/services/software-development/software-architect/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)
* [MLOps engineering](https://azendo.co/services/mlops-engineering/)
* [Software development](https://azendo.co/services/software-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [Azure — skill we assign for](https://azendo.co/skills/azure/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)
* [CloudFormation — skill we assign for](https://azendo.co/skills/cloudformation/)
* [Crossplane — skill we assign for](https://azendo.co/skills/crossplane/)

## Tell us what your roadmap needs Kubernetes for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)