← All posts
TAG

gitops

5 posts · browse all tags

  • 7 min readPaddy O'Cybear

    Building an Inner-Enterprise Loop with Kilter

    Enterprises don't have one software loop — they have two. A governed outer loop for the high-risk systems facing the outside world, and a vast, fast, transient inner loop: departmental tools, harness engineering, coordination portals, per-PR previews. Source-code management was built for the code. The inner-enterprise loop is bottlenecked on something else entirely — the orchestration and configuration of *running* software. That's the artifact that now matters, and it's where Kilter lives. `kilter package` is the seam that lets the inner loop feed the outer one without either compromising the other.

    architectureplatformgitopsdeveloper-experience
  • 7 min readPaddy O'Cybear

    GitOps Is the Control Plane

    Every platform team asks the same thing when a new deploy tool arrives — does it replace my GitOps, or feed it? Most tools answer wrong; they want to be the control plane. Kilter answers the other way. GitOps is the control plane; Kilter is an authoring tier that feeds it. Coming in late Q3, kilter apps promote seamlessly from a kilter-provisioned middle environment into pure-Kubernetes production reconciled by your ArgoCD — through your PRs, your RBAC, your audit. Same image, same chart, declared not injected.

    gitopsarchitectureplatformpaas
  • 6 min readPaddy O'Cybear

    Modern Kubernetes Is Delightfully Elegant and Almost Even Small

    I mapped every Kubernetes artifact that touches one production app — an agentic ITSM platform I run — and all of its dependencies. I expected sprawl. The whole declared app is three files and about ten concepts. The elegance is real. The smallness is 'almost,' because the last mile — namespace, identity, credentials against every shared service — is synthesized at runtime by an operator, not committed to git. Two control planes, git as the handoff. A trade, not a bug — and the path to actually small is clear.

    architecturek8genticgitopsplatform
  • 9 min readPaddy O'Cybear

    What Makes a Platform Agent-Native?

    A platform can run agents and still not be built for them. The difference is one design test, not a feature checklist: can an agent read a capability, edit it, and prove the edit worked — through text files and composable commands? Six principles fall out of that constraint, and they describe a product that looks nothing like a hosted console.

    agentsarchitectureplatformgitops