Orkestra Blog

Engineering deep-dives, release notes, and design thinking from the people building Orkestra.

5 min read

Why Orkestra?

Kubernetes has always promised declarative infrastructure. You describe what you want. The platform makes it so. That promise holds everywhere — until you need to extend Kubernetes …

Read more
5 min read

Your CRD Is Enough

The engineering argument for why the operator should have always been the CRD. In 2017, Kubernetes shipped Custom Resource Definitions as the stable mechanism for extending its …

Read more
5 min read

Why I Built This

A few years ago I went for an interview and didn’t get the job. The requirement was that the person knew how to write Kubernetes controllers and operators. Several of them. I …

Read more
4 min read

The Infrastructure is Gone

Orkestra does not give you a better way to build operator infrastructure. It removes it. Every operator author starts in the same place. Before a single line of business logic, …

Read more
9 min read

What If the Next Ops Is IntentOps?

Every generation of ops shifted what the primary artifact was. We might be due for another shift. A short history of shifting artifacts Every major ops movement of the last twenty …

Read more
5 min read

Three gates

Orkestra started with two places where you could decide whether something should happen: at admission (before the CR hits etcd) and inside the reconciler (once it was there). That …

Read more
7 min read

The Queue That Grew Up

There is a particular kind of cleanup pass that every solo builder knows. The one you do when the project has been growing fast and you finally let yourself look at the parts you …

Read more
4 min read

The Client That Carries Configuration

Every resource in Orkestra applies to Kubernetes via server-side apply. That patch call has one flag that matters more than the others: Force. When Force is true, the field manager …

Read more