OnCallReadyStart learning

Platform Engineering: Backstage & Crossplane

Build an internal developer platform: Crossplane v2 turns requests like "a small database" into cloud resources through your own Kubernetes APIs, and Backstage puts a catalog, templates and docs in front of it. Debug it on call, and keep it from deleting data.

In plain words

Imagine a big office where every team has to build its own desk, run its own power cable and call the electricity company before it can start working. A platform team is the office manager who builds a catalogue of ready desks: you fill in a short form, a desk with power, a network cable and a nameplate appears, and the manager makes sure every desk follows the fire code. Backstage is the catalogue and the form; Crossplane is the crew that builds the desks.

Why it matters on call

Platform engineering is where many SRE and DevOps careers go next, and it is also the work behind most "how do we let teams self-serve?" questions in interviews. On call you will be the person who debugs why a team's database request is stuck, why a template produced a broken service, or why a namespace refuses to die. This chapter gives you the model and the exact error messages so you can answer those quickly instead of guessing.

Lessons

  1. 42.1Platform engineering: what an internal developer platform is
  2. 42.2Crossplane v2: the Kubernetes API as a control plane
  3. 42.4Providers, functions and their credentials
  4. 42.6Managed resources: Synced, Ready, external names and policies
  5. 42.8Your own API: CompositeResourceDefinitions
  6. 42.9Compositions and function-patch-and-transform
  7. 42.12Debugging composite resources on call
  8. 42.14Changing a platform without destroying data
  9. 42.16Backstage and the software catalog
  10. 42.18Software Templates: the golden path as a form
  11. 42.20TechDocs and the Kubernetes plugin
  12. 42.31Putting it together: one golden path, end to end

19 hands-on labs (missions, incidents and drills) run in the terminal.

Open this chapter in the terminal Free, in your browser - a real Ubuntu terminal to try it in, with missions that check your work.

Questions people ask

Do I need the Kubernetes and AWS chapters first?

Yes. Crossplane runs on Kubernetes and everything it builds is a Kubernetes object, so you need objects, RBAC, CRDs and Helm. The cloud resources in the labs live in the simulated AWS account from the AWS chapters, and Backstage reads repositories from git.lab, the server of the delivery chapters.

Which versions does the chapter use?

Crossplane v2.4.2 with the crossplane CLI v2.5.0, function-patch-and-transform v0.11.1, provider-kubernetes v1.4.1, the AWS providers v2.9.0 and Backstage 1.56. They were checked against the projects' releases in October 2026; both projects ship often, so check the release notes before you rely on a detail.

What is simulated in the labs?

The provider and function pods are placeholders whose controllers run inside the simulator, Backstage has no frontend of its own (Console > Backstage plays that part) and only reads git.lab, and claims from Crossplane v1 are not modelled. Conditions, events, names and error messages follow the real source code.

Is this the same as Terraform?

Both create cloud resources from declarations, but Terraform changes the world when someone runs apply, while Crossplane's controllers reconcile continuously, correct drift on their own and use Kubernetes RBAC and GitOps instead of a state file. Many companies use both: Terraform for the foundations, Crossplane for self-service APIs.

Do I have to use Backstage and Crossplane together?

No. Backstage works with any backend, and Crossplane works without a portal. They are combined here because they are the most common open-source pair: the portal is where people find and start things, and the control plane is where requests become real resources built the same way every time.