Jonathan Lalou's Blog

Lecturer

Eros Taborelli is a Software Architect at Julius Baer, with over 15 years in IT spanning telecommunications, e-commerce, fintech, security, and AI. He focuses on enterprise architecture, platform engineering, and modernizing software delivery. Relevant links include his LinkedIn profile (https://ch.linkedin.com/in/erost).

Abstract

This article probes Eros Taborelli’s narrative on Julius Baer’s decentralized control plane for orchestrating platform services. It examines motivations for eschewing centralized portals, adopting Crossplane for Kubernetes-based infrastructure as code, and fostering organizational alignment. Through methodological dissection, it evaluates GitOps integration, custom resource definitions, and implications for DevOps efficiency in financial institutions.

Motivations and Shortcomings of Traditional Approaches

Eros frames Julius Baer’s DevOps platform, supporting dozens of teams and hundreds of applications. Developers interact via Git-based version control, CI/CD pipelines scanning, testing, building artifacts for registries, and deploying to infrastructure. Traditionally, resource provisioning occurs via self-service portals—forms yielding virtual machines or databases post-approval. Analogous to online shopping or conference registration, portals offer immediate feedback, red-flagging invalid inputs. Yet, shortcomings abound: Every operation requires implementation, audits demand custom integrations, differences between environments necessitate manual reviews. Silos emerge—product teams (CI/CD, data streaming, cloud) build isolated automations, burdening integration on central entities. Eros critiques this: Portals hinder GitOps and infrastructure as code (IaC), lacking auditability, composability. Contexts: Financial regulations mandate traceability; silos stifle agility. Implications: Centralized models foster dependency, delaying deliveries.

Adopting Crossplane for Decentralized Orchestration

To dismantle silos, Eros advocates Crossplane, a CNCF project extending Kubernetes for IaC. Custom resource definitions (CRDs) model resources (databases, clusters) as Kubernetes objects, reconciled by controllers to external APIs. “Fleet Commander” decentralizes: A central “commander” cluster ingests compositions—high-level APIs aggregating low-level resources. Provider Kubernetes pushes these to “unit” clusters near target infrastructure, executing via specialized providers. Methodology: GitOps workflows—developers commit YAML manifests to repositories; Flux synchronizes to commander. Compositions decompose into managed resources, pushed to units for reconciliation. Code exemplifies:

apiVersion: database.crossplane.io/v1beta1
kind: CloudSQLInstance
metadata:
  name: my-db
spec:
  forProvider:
    databaseVersion: POSTGRES_13
    region: us-central1
    settings:
      tier: db-f1-micro

This CRD provisions a Google Cloud SQL instance. Contexts: Aligns with platform engineering—internal platforms as products. Implications: Empowers teams owning automations, central governance ensures consistency.

Organizational and Technological Synergy

Eros emphasizes reciprocity: Technology shapes organization, vice versa. Decentralization assigns automation to product teams, central authority governs APIs via CRDs, forming a service catalog. Custom providers address gaps—e.g., Azure’s missing features. Internal compositions in units encapsulate logic, exposing simplified APIs. GitOps ensures traceability: Commits log changes, audits via repository history. Composability allows reusing definitions across environments. Implications: Reduces bottlenecks, enhances scalability. Challenges: Learning curve for Crossplane; ensuring unit proximity minimizes latency.

Implications for Enterprise DevOps

Fleet Commander provisions diverse services—onboarding, Kubernetes, cloud resources, continuous delivery, Kafka—via units. Open-sourcing custom providers contemplated, but core framework remains internal due to specificity. Broader ramifications: Promotes autonomy, aligns with GitOps, fosters innovation. In finance, bolsters compliance through auditable IaC. Future: Expand offerings, refine governance. In summation, Eros’s model exemplifies symbiotic evolution of structure and tools for agile platforms.

Links:

• Lecture Video
• Eros Taborelli on LinkedIn