---
title: "Crossplane | Skills We Assign For | Azendo"
description: "Crossplane for Kubernetes-native infrastructure — continuous reconciliation, platform abstractions, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/crossplane/"
---

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

# Crossplane.

Crossplane manages cloud infrastructure through the Kubernetes API. Databases, queues and buckets are declared as Kubernetes resources, so the cluster's reconciliation loop continuously enforces the desired state rather than applying it once.

## Where Crossplane fits on a long engagement.

Continuous reconciliation is the meaningful difference from apply-based tools. Terraform enforces state when someone runs it; Crossplane enforces it constantly, so a resource changed by hand is corrected rather than merely reported as drift at the next plan.

Its more ambitious use is composition: defining an abstraction like "a production database" that developers request without knowing the underlying provider configuration. That is genuinely powerful and genuinely complex, and a platform team that builds it without the capacity to maintain it has created a dependency rather than a capability.

## What an assigned team does with Crossplane.

Platform abstractions are a commitment, not a project. Every abstraction you publish is an interface other teams now depend on, with versioning, documentation and support obligations that continue indefinitely.

Taking that on without standing capacity behind it is how internal platforms become the thing nobody will touch. What a standing commitment covers is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Crossplane for.

* Infrastructure that self-corrects Manual changes reconciled away continuously rather than reported at the next plan.
* One control plane for cluster and cloud Application and infrastructure declared through the same API and the same review path.
* Abstractions developers can self-serve A reviewed "production database" definition, so teams request rather than assemble.

## How Crossplane capacity is assigned.

Crossplane work is assigned under [devops managed services](https://azendo.co/services/cloud-and-devops/), with the maintenance obligation of any published abstraction stated before it is built.

## Roles we assign Crossplane for

* [Platform Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/platform-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

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

## Related in cloud and infrastructure

* [Kubernetes — skill we assign for](https://azendo.co/skills/kubernetes/)
* [Docker — skill we assign for](https://azendo.co/skills/docker/)
* [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/)

## Tell us what your roadmap needs Crossplane 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/)