Wrap-up ⏱️ 5m
Three hours ago you had a kubeconfig and no cluster state. Now you have:
| Module | You built |
|---|---|
| Connect to your cluster | A working kubectl pointing at your workshop cluster |
| Install Crossplane | Crossplane running in crossplane-system |
| Providers & first MR | provider-kubernetes installed and managing one Object |
| Define an Application | An Application XRD + Composition + one XR that composes into five real resources |
| Modify your Application | A Composition edit that reshaped the frontend without touching the XR |
That last point is the one worth taking home. A Composition change reshaped real resources without the consumer doing anything. That's the primitive real platforms are built on.
7.1 Where to go next
Practical next steps
- Install a cloud provider.
provider-aws-family,provider-gcp, orprovider-azuregive you real infrastructure instead ofConfigMaps. Same XRD/Composition shape you already know. - Try another composition function.
function-kclorfunction-go-templatingget you out of YAML patches into real programmatic composition. - Look at real-world platforms. Upbound Marketplace and the Crossplane examples repo show what production compositions look like.
Concepts we didn't cover
The workshop kept scope tight on purpose. The big topics we skipped:
- Claims vs. XRs — the v1 pattern. Still seen in older repos; covered in the Cheatsheet §1.3.
- Operations — Crossplane's newer construct for imperative one-shot work (migrations, repairs). Operations docs.
- Package management —
Configurationpackages let you ship your XRD + Composition together as one installable unit. Configuration packages docs. - Policy and ValidatingAdmissionPolicy. Crossplane XRs work with Kubernetes' admission ecosystem; you can gate them, mutate them, and enforce org-wide rules.
7.2 Feedback
Two minutes of feedback from you today shapes the next run of this workshop. Fill in whatever you can, skip the rest.
Open the feedback form (your instructor will share the real URL in chat)
Anonymous. No wrong answers. If one thing broke or one thing clicked, we want to know.
7.3 Thanks
Thanks for spending an afternoon on this. Leave your cluster running as long as you like — experiment, break things, come back in a week. The Crossplane Slack is friendly and the maintainers hang out there.
See you at the next one.