Skip to main content
Hi, I’m Nourhan Mohamed — welcome to this beginner course on Crossplane. Over the next lessons we’ll install Crossplane, connect it to the platforms you want to manage, and compose infrastructure into simple, reusable building blocks that your team can request on demand.
A slide titled "What you'll learn" with three numbered items. The items are: "Install Crossplane on Kubernetes," "Manage platforms with providers," and "Compose self-service infrastructure."
Let’s dive in. Conceptually, Crossplane makes your Kubernetes cluster into an infrastructure control plane. Instead of hopping between cloud consoles or asking other teams to provision resources, you declare the infrastructure you need in Kubernetes manifests and Crossplane provisions and continuously reconciles those resources. To picture this, imagine a busy restaurant. As a diner you don’t go into the kitchen — you place your order with a waiter, the kitchen checks for required details if anything is missing, then prepares your meal and corrects any mistakes. Crossplane plays the role of the waiter and kitchen: you submit a request (YAML), Crossplane validates and fulfills it, and continuously ensures the result matches your intent.
An illustrated infographic titled "Think of a busy restaurant" showing three steps: a customer ordering at a table, a waiter taking the order, and a chef cooking the meal. Each step is labeled "You order," "Waiter takes it," and "Kitchen makes it."
Modern applications require more than containers: databases, storage buckets, networking, and many cloud services. Managing all of that across separate consoles leads to configuration drift and fragile manual processes.
A simple architecture diagram showing a central "Your app" box with arrows to resource cards labeled Database, Storage bucket, Network, and "...a dozen more."
Crossplane solves this by letting you declare managed resources as Kubernetes objects. For example, a generic managed resource looks like this:
When you apply such YAML, Crossplane:
  • validates the request (ensures required fields and credentials are present),
  • provisions the real infrastructure,
  • and continuously reconciles the external resources to match the declared state.
This three-step flow — apply YAML, validate, and provision — is the core of how Crossplane turns Kubernetes into an infrastructure control plane.
A three-step flow diagram titled "From request to running infra" showing: 01 Apply YAML (no console clicking), 02 Validate (check requirements), and 03 Provision (create real infra). Each step is in a rounded box with icons and arrows connecting them.
Crossplane extends Kubernetes by installing CustomResourceDefinitions (CRDs). Kubernetes already understands built-in types like Pods and Services; Crossplane adds CRDs for resources such as databases and buckets. Once added, infrastructure appears as first-class Kubernetes resources that can be created, inspected, and stored in Git alongside application code.
A diagram titled "Crossplane extends Kubernetes" showing the Kubernetes API with built-in resources (Pod, Service) on the left and Crossplane-added custom resources (Database CRD, Bucket CRD) on the right.
CustomResourceDefinitions (CRDs) are how Kubernetes learns new resource types. After installing Crossplane, inspect CRDs with kubectl get crd and list Crossplane API resources with kubectl api-resources | grep crossplane.io. For more, see the Kubernetes CRD docs.
Installing Crossplane with Helm Crossplane is commonly installed via Helm. The main steps are:
  • Add the Crossplane Helm repository and update your local cache.
  • Install the Crossplane chart into the crossplane-system namespace (Helm can create it).
  • Verify the Crossplane controllers are running and that new API resources are present.
You will need sufficient cluster privileges (typically cluster-admin) to install CRDs and controllers. If you don’t have permissions, ask your cluster administrator to install Crossplane or grant the required RBAC.
Commands (copy/paste):
Verify the Crossplane pods are running:
List Crossplane API resources to confirm CRDs and controller-added resources:
You should see API groups ending with crossplane.io. These are the new resource types Crossplane adds. Summary table — quick reference Next steps
  • Connect Crossplane to a cloud provider using a provider package (we’ll cover provider installation and credentials in the next lesson).
  • Learn how to define managed resources (databases, buckets, networks) and how to compose them into higher-level, self-service APIs for your teams.
References

Watch Video

Practice Lab