-
Book Overview & Buying
-
Table Of Contents
The Platform Engineer's Handbook
By :
We chose Crossplane because our previous approach of manual provisioning through tickets had become untenable. Every database request meant context-switching, tribal knowledge about which parameters mattered, and no audit trail when something broke. The moment Crossplane clicked for us was realizing that infrastructure could live in the same Git repository as application code, reviewed by the same people, versioned with the same tooling. That alone justified the investment.
But we won't pretend it's painless. Composition debugging remains frustrating. When something fails, you're often left running kubectl describe across multiple resources trying to trace where the reconciliation went wrong. The learning curve is steeper than the "it's just Kubernetes YAML" pitch suggests; the object model (XRDs, Compositions, Claims, Managed Resources) takes time to internalize, and your team will make mistakes...