AI inference on GPU Kubernetes
Running GPU-backed Kubernetes clusters that serve BHASHINI's speech-to-text, text-to-speech, and translation models as containerised microservices on India's sovereign government cloud.
Currently keeping GPUs busy at Bhashini
Lead DevOps Engineer | AI Infrastructure | AWS Solutions Architect | MBA
I build the quiet parts behind reliable software — including the GPU platforms that AI models actually run on.
AWS, Kubernetes, GitOps, CI/CD, and observability — currently running GPU-backed clusters that serve speech and translation AI models for a national platform.
Impact
Measurable results from AI inference platforms, cloud infrastructure, fintech systems, and enterprise engineering tooling.
Running GPU-backed Kubernetes clusters that serve BHASHINI's speech-to-text, text-to-speech, and translation models as containerised microservices on India's sovereign government cloud.
Architected Jenkins and ArgoCD pipelines across 5 microservices, reducing deployment cycle time by approximately 60% and removing 90% of manual release intervention.
Managed production clusters at 10M+ user scale, using namespace governance and resource quotas to reduce infrastructure over-provisioning by 30% while sustaining 99.9% uptime.
Built Prometheus, Grafana, and ELK observability, cutting detection time by 50% and reducing MTTR from 45 minutes to under 15 minutes.
Administered GitHub Enterprise, Jira, and Confluence Data Center for 30,000+ engineers with 99.95% platform availability and zero-downtime upgrade cycles.
Use LLM assistants day to day to scaffold Terraform and Ansible, triage noisy log output, draft RCAs, and turn tribal knowledge into runbooks — every generated change reviewed before it reaches a cluster.
AI platform
AI models are only useful once something keeps them running. That part is DevOps — GPU capacity, scheduling, rollouts, and the signals that tell you an inference service is degrading before users do.
Current work — Bhashini, Govt. of India
BHASHINI is India's national language platform under MeitY: speech-to-text, text-to-speech, and translation across Indian languages, exposed as APIs that other government and public services build on. I run the Kubernetes layer those models are served from, on Yotta's sovereign Government Community Cloud.
The operational problem is not the model — it is GPU capacity that is scarce and expensive, inference pods that behave nothing like stateless web services, and a release process that has to ship model containers without dropping live traffic.
01 — Capacity
Scheduling inference workloads onto GPU nodes: node labelling and taints so only GPU workloads land on GPU hardware, resource requests and quotas per namespace, and placement rules that stop one team's batch job from starving a live service.
02 — Delivery
Model images are large, slow to pull, and slow to warm up. Pipelines are built around that: registry hygiene, image promotion between environments, staged rollouts, and health gates that wait for a model to actually be ready rather than for the process to merely start.
03 — Leverage
LLM assistants are part of my daily loop: scaffolding Terraform and Ansible, reading through noisy log dumps during triage, drafting RCAs from incident timelines, and converting fixes into runbooks. Useful for the first draft — never for the last word. Generated changes get reviewed like any other diff.
Technical skills
A production-heavy toolkit across AI workload infrastructure, AWS architecture, delivery automation, containers, infrastructure as code, monitoring, incident management, and Linux operations.
Professional experience
Tarento Group
|
Client:
Bhashini (Govt. of India)
Persistent Systems
|
Client:
Intuit
Codewalla Software
Development
|
Client:
1Huddle
Built and running
A self-hosted platform I designed, built, and operate end to end — the same discipline as day job work, with nobody else to hand the pager to.
Product · self-hosted
Endpoint and SSL certificate monitoring: a FastAPI service and an independent check worker sharing one image, Postgres for history, Redis for rate limiting, and a React dashboard. Incidents only open after a failure is confirmed from a second network vantage point, so a bad path from one host does not page anyone at 3am.
Platform · GitOps
Jenkins, Argo CD, the Kubernetes Dashboard and InfraSight running on one small cloud box behind NGINX, each on its own hostname with automated TLS. Manifests live in a Git repo as a Kustomize base plus per-environment overlays; Argo CD reconciles, so a rollback is a revert rather than an archaeology exercise.
Delivery · CI/CD
A Jenkins multibranch pipeline builds container images and deploys by committing the new tag to the manifest repo — CI never touches the cluster. Main goes to production; every other branch gets its own namespace and overlay, generated on first build.
Background
Certification
SAA-C03
VPC design, IAM, RDS, disaster recovery, and production hardening — the same areas I work in daily.
View on CredlyEducation
Contact
Best fit: teams that need hands-on ownership across GPU and AI workload infrastructure, AWS, Kubernetes operations, CI/CD automation, observability, and incident response.