Uploaded April 2026 | Updated September 2026, 3 weeks ago
Break the silo: How we built a decentralized control plane for service orchestration by Eros Taborelli
At Julius Baer we are building an internal platform to support dozens of DevOps teams in delivering and operating hundreds of applications.
With different product teams delivering their own offerings like, but not limited to, CI/CD, data streaming, or public cloud services, we hit a crossroad: how are we going to enable access to those platform capabilities in an easy and consistent way, while at the same time promote methodologies like GitOps and Infrastructure as Code.
Traditionally, each team would build their own automation in a vacuum, leaving to someone else integrating it and providing a simple interface to users, likely in the form of an ordering portal.
Instead, let us walk you through the journey where organizational models and technology shape each other, resulting in us adopting a decentralized Crossplane setup to keep automation responsibilities close to the product teams while at the same time enabling a consistent public API governed by a central authority, effectively a Service Catalog built upon Kubernetes’ Custom Resource Definitions.
Break the silo: How we built a decentralized control plane for service orchestration by Eros Taborelli
At Julius Baer we are building an internal platform to support dozens of DevOps teams in delivering and operating hundreds of applications.
With different product teams delivering their own offerings like, but not limited to, CI/CD, data streaming, or public cloud services, we hit a crossroad: how are we going to enable access to those platform capabilities in an easy and consistent way, while at the same time promote methodologies like GitOps and Infrastructure as Code.
Traditionally, each team would build their own automation in a vacuum, leaving to someone else integrating it and providing a simple interface to users, likely in the form of an ordering portal.
Instead, let us walk you through the journey where organizational models and technology shape each other, resulting in us adopting a decentralized Crossplane setup to keep automation responsibilities close to the product teams while at the same time enabling a consistent public API governed by a central authority, effectively a Service Catalog built upon Kubernetes’ Custom Resource Definitions.
