From Snowflake Servers to Snowflake Clusters - The GitOps Journey
summary
MasterCard enforces one dedicated cluster per application and reduces drift by standardizing three cluster types: control cluster (one per environment), single‑tenant and multi‑tenant. Clusters provision automatically: a Git change triggers Concourse, PKS API creates a cluster (default three masters), a Kubernetes job runs kustomize/Helm overlays and Argo CD reconciles desired vs actual state. Base services include Prometheus+Thanos, Fluent Bit → Elasticsearch/Kibana, Vault for secrets; teams can request tens to hundreds of clusters via CRD definitions.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:20Topics
- 0:41Patterns & Snowflakes
- 1:51Problem
- 5:22Timeline
- 8:23On-Prem Infrastructure
- 9:08Creating New K8s Clusters
- 10:27Control Cluster
- 11:04Single Pane of Glass - Monitoring
- 12:37Single Pane of Glass - Logging
- 13:21Unified CD Strategy
- 14:41Kustomize Overview
- 17:13Cluster Creation and Provisioning.
- 19:45CRD - Cluster Spec
- 21:09CRD - Mapping Spec
- 23:27Argo CD Application
- 24:01Future Plans
- 25:02Takeaways
related talks
26mManaging GitOps Deployments in Multi-cluster Production Environments
29mTales from the Branches: GitOps in the Real World
35mKubernetes journey
29mA Multi-Cluster, Multi-Cloud Infrastructure with GitOps at CERN
43mConfiguration as Data, GitOps and Multi Cluster The Key to Successful Servic
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
32mDon't Start With 500 Clusters: Patterns in Scaling Multi-Cluster Kubernetes…