Case study · Fintech · Continuous delivery
50% faster go-to-market with an Argo CD implementation for Klub, one of India's largest revenue-based financing investors.
Klub · Revenue-based financing
No self-healing, no rollback, no drift detection across many microservices. We put GitOps in front of all of it.
50%
Faster go-to-market
Minutes
Deployment time, down from days
The opportunity
Many microservices, deployed independently, with no way back.
With the platform on Kubernetes, Klub's remaining constraint was delivery. Containers had no self-healing, so accidental deletion of a container or another Kubernetes resource was a genuine business risk.
The applications' architecture ran multiple microservices needing independent deployment and management. Rollback of an application or its configuration was crucial and not straightforward, and there was no dashboard to detect configuration drift.
No self-healing
Accidental deletion of containers or Kubernetes resources was a business risk.
Microservices deployed independently
A complex architecture meant many moving parts to manage separately.
Rollback was crucial and hard
Reverting an application or configuration change mattered and was not simple.
No drift detection
There was no dashboard to surface configuration drift.
The impact
Days of deployment became minutes of pipeline.
Commit is the deployment
Developers commit to Git; Argo CD detects the change and deploys to the right environment.
Configuration as code
Declarative configuration management removed manual configuration changes entirely.
Consistent across environments
The same declarative source deploys everywhere, reducing error risk and improving quality.
Visible deployment process
Greater visibility means issues are identified and troubleshot faster.
The stack
What it runs on.
- Continuous delivery
- Argo CD, GitOps workflow
- Source of truth
- GitHub, Infrastructure as Code
- Traffic
- ALB ingress controller
- Platform
- Kubernetes on Amazon EKS
The road ahead
Delivery is declarative. That is what makes it safe to change.
With every change tracked in Git and drift visible on a dashboard, higher-risk releases become a matter of progressive delivery rather than of caution.
- 01
Progressive delivery on risky changes
- 02
Automated drift remediation
- 03
Wider self-healing coverage
Talk to us
Bring one process. Leave with an outcome architecture.
30 minutes on one function, mapped to the architecture behind it. No slides.