Cyscale's Journey on Kubernetes
summary
Starts from ClickOps, a single umbrella Helm chart and latest tag deployments, then builds a Terraform-provisioned GitOps platform using Argo CD GitOps and per-service Helm charts; team grows from ~6 to ~16 and services from ~7 to ~30. Chooses NATS for messaging (simple pub/sub) and picks Istio for a service mesh to gain mTLS, traffic control and proxy-level observability. Moves MySQL to RDS and Neo4j to dedicated VMs for performance; Helm Secrets handles secrets. Overall the GitOps + Argo workflow and infrastructure shifts work and reduce operational toil.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:44Engineering versus business needs
- 4:12Choosing technologies with practical constraints
- 7:46Kubernetes journey timeline
- 9:12Service mesh and messaging adoption
- 11:00GitOps and infrastructure as code
- 13:28Service mesh alternatives and challenges
- 16:20Messaging system selection
- 18:11Kubernetes secrets management
- 19:59CI/CD challenges and GitOps
- 22:05Databases on Kubernetes or external
- 25:14Resource management and cloud costs
- 27:41Final tips and reflection
- 28:25Q&A
related talks
28mGitOps with Argo CD and Helm: Managing Your Kubernetes Repository
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
20mScale production grade K8s Multi-Cluster environments using GitOps
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
02h 47mA GitOps Architecture from Scratch: Gitlab, Ansible, Terraform, Kub and AWS
30mManage your kubernetes cluster in the GITOPS way !!
36mMulti-Cluster Kubernetes Quick Delivery with IaC and GitOps
02h 38mStop using kubectl, and use Git instead! - Hands-on GitOps workshop using Argo CD and Helm