2 posts tagged with "GitOps"

Our platform manages where and how services are deployed through GitOps repositories. But what about the application itself — the code, the build, the container? Until now, every team set up their own Dockerfile, wrote their own CI pipeline, and figured out their own image tagging strategy. The result was predictable: 10 teams, 10 different CI workflows, 10 different container build approaches, and zero consistency.

The Application Repository convention changes this. When a new service is scaffolded via Backstage, it delivers a complete, opinionated repository with source code, Dockerfile, CI pipeline, and a .k8s folder — giving the application team autonomy over their workload configuration while keeping the platform in control of the deployment model.

Every platform team reaches the same inflection point. The ticket queue grows faster than the team. Engineers wait days for a namespace, a database, or an ArgoCD application — things that should take minutes. The platform team becomes the bottleneck for every team trying to ship.

We hit that wall. This post is about how we got out of it.