Building a Production Multi-Cloud Cluster Platform
Putting the full platform together with everything learned in the series.
Read articleI help teams adopt Kubernetes and cloud native platforms through platform engineering, Crossplane based infrastructure automation, GitOps workflows, and SRE practices. Remote, worldwide.
Engagements typically focus on one of the following areas.
Design and build self-service platforms that reduce cognitive load and accelerate delivery for your engineering teams.
Implement Crossplane compositions, providers, and operating models for declarative infrastructure management at scale.
Plan and execute bare metal to cloud migrations with minimal disruption, including architecture design and workload modernization.
Modernize legacy applications with containers and establish cloud native delivery patterns, CI/CD pipelines, and runtime best practices.
Kubernetes adoption, cluster design, security hardening, and reliability foundations with SLOs, observability, and incident readiness.
Short call and review of current stack, constraints, and desired outcomes.
Target architecture, delivery roadmap, risks, and trade-offs aligned to your teams.
Implementation and productionization with documentation, runbooks, and handover prep.
Training, enablement, and next-step planning so teams can operate independently.
Internal Developer Platform architect focused on platform reliability, delivery workflows, and infrastructure automation.
Built observability platforms and operated multi-cloud Kubernetes infrastructure for production workloads.
Technical referent for Kubernetes foundations supporting critical financial services.
Led containerization initiatives and early GitOps adoption for legacy application modernization.
Problem: Bare-metal provisioning needed the same declarative workflows as cloud resources.
Approach: Built a Crossplane provider and compositions to expose MAAS resources as Kubernetes APIs.
Result: Consistent infrastructure requests and reusable abstractions for platform teams.
Problem: Teams needed self-service infrastructure with guardrails and consistent delivery.
Approach: Defined platform building blocks, GitOps governance, and Crossplane abstractions.
Result: Faster onboarding and repeatable platform patterns across environments.
Problem: Teams needed observability with isolation, secure access, and consistent SLOs.
Approach: Designed tenant-aware telemetry pipelines with strong identity and mTLS.
Result: Reliable dashboards, trusted telemetry, and clear operational ownership.
Newest posts from the series. Read the full series on the blog.
Putting the full platform together with everything learned in the series.
Read article
Bring in existing resources and evolve toward declarative management.
Read article
Automate testing and releases for Crossplane function development.
Read articleThe Linux Foundation / CNCF
ID: LF-svrxqtbxri • Oct 2021
Verify CKA on Credly →Sorbonne Paris-Nord
Sep 2017 – 2021