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 moreFrom the team
Orkestra Blog
Engineering deep-dives, release notes, and design thinking from the people building Orkestra.
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 moreWhy Operators Are Over-Permissioned — And How We Fixed It
Most Kubernetes operators are massively over-permissioned. Not slightly, not accidentally — structurally. Inspect the RBAC of a typical production operator and you will find …
Read moreWhy 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 moreThe 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 moreThere Is No Kubernetes Expression Language
So I built one. Every team that operates Kubernetes eventually writes the same functions. hasCrashingPod. rolloutComplete. allReplicasReady. isTerminating. The names vary slightly. …
Read moreWhat 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 moreI've Been Trying to Describe Orkestra in One Sentence for Two Years
And every time I thought I had it, the project outgrew the words. I shipped the first version of Orkestra with a GitHub description that said: “Declarative runtime for …
Read more