~/ shubham tatvamasi

I build thequiet machinerybehind intelligentsystems.

GPU sharing, LLM serving and Kubernetes platforms, from a single node to fleets of clusters, engineered so models run fast, GPUs never sit idle and nothing goes dark.

$ now orchestratingGPUs▍
scroll
  • Kubernetes✦
  • vLLM✦
  • SGLang✦
  • KServe✦
  • NVIDIA Dynamo✦
  • NVIDIA NIM✦
  • llm-d✦
  • Envoy AI Gateway✦
  • LiteLLM✦
  • NVIDIA GPU Operator✦
  • AMD GPU Operator✦
  • DCGM✦
  • Kubernetes DRA✦
  • MIG✦
  • Kueue✦
  • KAI Scheduler✦
  • GuideLLM✦
  • Prometheus✦
  • Grafana✦
  • KEDA✦
  • Flux CD✦
  • Argo CD✦
  • Terraform✦
  • Ansible✦
  • Go✦
  • Helm✦
  • Rook-Ceph✦
  • Gateway API✦
  • WireGuard✦
  • ML-KEM✦
  • ML-DSA✦
  • OpenStack✦
01 · About

Most people meet AI through a chat box. I live one layer down, where tokens become GPU cycles, GPU cycles become heat, and a single misrouted request can idle a rack. My work is making that layer boring in the best way: declarative, observable, self-healing, and secure enough that nobody has to think about it.

12+years building Kubernetes platforms across cloud, hybrid and edge
80+clusters reconciled by Flux CD. Git is the source of truth
900+edge devices on post-quantum encrypted links
02 · Craft

Six layers, one obsession

Making the whole stack, from the GPU die to the API gateway, behave like one calm, observable, self-healing system.

/01 serving

Inference platforms

One control plane for models served through KServe, NVIDIA Dynamo, NIM, vLLM and SGLang. Model-aware routing through Envoy AI Gateway and llm-d, budgets and keys via LiteLLM, GuideLLM benchmarks, and autoscaling that adds replicas before it adds GPUs.

/02dcgm

GPU sharing & visibility

Telling allocated apart from actually computing. DRA with MIG, MPS and time-slicing, Kueue and KAI queues, and NVIDIA and AMD telemetry that catches idle, faulty and oversubscribed GPUs.

/0324/24 ready

Platform engineering

Controllers, CRDs and operators in Go. Multi-cluster networking, tenant isolation and HA storage that heals itself.

/04flux

GitOps everything

Flux CD reconciling 80+ clusters. If it isn't in Git, it doesn't exist.

/05ml-kem-768

Quantum-safe security

Post-quantum key exchange, signatures and certificate lifecycles, automated as Kubernetes-native resources.

/06 wg0 up

Edge & hybrid networks

Encrypted tunnels from 900+ devices behind carrier-grade NAT to private and public clouds. Fleets that stay reachable, observable and patched no matter where they live.

03 · Principles

How I think

A short operating manual for the systems I build, and the way I build them.

  1. 01

    Declare, don’t click.

    Every cluster, model and secret should be reproducible from a commit. If a human has to remember it, it will be forgotten.

  2. 02

    Measure the real thing.

    Allocated isn’t utilised. Ready isn’t responsive. I chase the metric that tells the truth, not the one that looks good on a dashboard.

  3. 03

    Scale the cheap layer first.

    Replicas before nodes, caches before GPUs, routing before hardware. Efficiency is a design decision, not a cost report.

  4. 04

    Secure for the next decade.

    Harvest-now, decrypt-later is real. Post-quantum crypto belongs in today’s pipelines, not tomorrow’s roadmap.

  5. 05

    Open by default.

    The best infrastructure ideas get sharper in public. Ship it, document it, let others break it.

04 · Shell

>_ Talk to the cluster

A tiny, very real-feeling terminal. Type help to look around, or try nvidia-smi.

shubham@control-plane: ~ctx: prod