7 posts tagged with "OpenChoreo"

Azure gives teams the infrastructure to run applications. But infrastructure alone doesn't tell developers how to get a service into production: where to register it, how to request a database, which environments they can deploy to, and where to look when something fails. Platform teams need to make those steps consistent across services while keeping control over the infrastructure underneath.

For platform engineers already running workloads on AKS, the remaining work is turning Azure services into a self-service path for developers. OpenChoreo, an open-source developer platform, is one way to build that path on top of what the team already runs.

Introduction to IDPs​

An internal developer platform (IDP) is a self-service platform that gives developers (and AI agents) standardized, repeatable ways to ship and operate software without requiring them to understand all of the underlying infrastructure and tooling, or depend on platform and operations teams to perform routine tasks on their behalf.

OpenChoreo can provision managed infrastructure, such as databases and caches, through Crossplane. In our post on self-service resources, we described how a ResourceType can point at whatever provisioner a platform team already uses, Crossplane included. The new Crossplane integration is a working example of that. It provisions PostgreSQL and Redis through Crossplane v2, and its ResourceTypes and Compositions are ready to try as they are, or to copy and adapt for your own platform.

There is more than one way to put Crossplane behind a ResourceType. The integration takes one opinionated position: the data plane decides how a resource is built. This post walks through the options, the trade-offs of the one we picked, and the contract between OpenChoreo and Crossplane that makes it work.

こんにちは (Konnichiwa)! I wanted to share a quick update on OpenChoreo at KubeCon + CloudNativeCon Japan 2026, which is just next week. Fresh off our first KubeCon in Amsterdam, we're excited to bring OpenChoreo to the community in Japan as a CNCF Sandbox project. If you're heading to Japan, we'd love to meet you.

Here are some opportunities for you to connect with us in Japan.

OpenChoreo v1.1 shipped recently, and one of the headline features is resource abstractions: a way to treat managed infrastructure like databases, queues, and caches as first-class, declarative dependencies of a workload. Platform engineers publish reusable ResourceType templates. Developers self-serve a Resource from one of those templates (picking the type, filling in only the parameters they care about) and wire its outputs into their Workload, the same way they already reference other components' endpoints.

This post walks through the model, the new CRDs that back it, and a real example you can install: a small collaborative document editor called Doclet that depends on Postgres and NATS.

We're very excited to announce that OpenChoreo has been accepted into the Cloud Native Computing Foundation (CNCF) Sandbox.

Before anything else, we want to give a huge shoutout to everyone who has been part of this journey. To our contributors, early adopters, and community members who filed issues, asked hard questions, and pushed the project forward. This milestone belongs to you. A sincere thank you to the CNCF team for their guidance and for giving us the space to present and discuss OpenChoreo with the broader community.

But we didn't want to stop there. Alongside the CNCF acceptance, we're also shipping OpenChoreo 1.0, our first production-ready release.

Two milestones, one moment, and a community that made both possible.

Hello everyone. I wanted to share a quick update on OpenChoreo at KubeCon EU 2026, which is just two weeks away. I'm thrilled to tell you that OpenChoreo will be there for the first time as a CNCF Sandbox project. If you're heading to Amsterdam, we'd love to meet you.

Here are some opportunities for you to connect with us in Amsterdam.