Custom Resources, Not Custom Forks - Curating OpenChoreo for Your Enterprise

OpenChoreo ships with sensible defaults, but they will not survive first contact with your organisation. No project ships your regulator, your data classification model, or your definition of "ready for production." With data residency and sovereignty requirements increasingly shaping enterprise architecture, that gap is no longer just a design consideration.

This session is about what you do next. Rather than a tour of extension points, it works through a scenario: five successive additions to an OpenChoreo platform over fourteen months at a financial services company operating in three African jurisdictions.

Well see from a ComponentType that turns an architecture standard into a schema developers cannot violate, to a Trait that makes a non-compliant deployment impossible to render, to a governed build pipeline and self-service in-country infrastructure.

The through-line is cost and maintainability: each addition is cheaper than the one before it, none requires building a Kubernetes controller, and none requires forking OpenChoreo. The result is a platform tailored to the enterprise you actually have, without losing the ability to evolve with upstream OpenChoreo.