AI Infrastructure Roadmap

The 2026 skillset

LLMs and GPUs the way production runs them: local inference foundations, GPU sharing, the MLOps stack real platforms are built on (Kubeflow, KServe, batch scheduling), and LLMOps/AIOps for day 2.

5 stages ยท 16 resources ready ยท 13 in the works, all free ยท every stage ends with a checkpoint you can verify on a real cluster

Your journey: 16 steps. Check them off as you go, this page remembers.

Local LLM foundations

~1-2 weeks

Before Kubernetes, GPUs, or platforms: understand how inference actually works on hardware you control.

โœ“ Checkpoint: you can now

Run a model locally and explain tokens per second, quantization, and the memory math.

โšก Prove it

Run the same model at two quantization levels and measure the speed and quality difference.

GPUs on Kubernetes

~2-3 weeks

GPUs are the scarcest resource in the building. Learn to share them without wasting them.

DRA: dynamic resource allocation explainedguide coming

โœ“ Checkpoint: you can now

Share one GPU across workloads and defend your strategy: MIG vs time-slicing vs HAMi.

โšก Prove it

Slice a GPU with MIG (or simulate with HAMi) and run two isolated workloads on it.

Training & MLOps platform

~2-4 weeks

One model on one GPU is a demo. Teams need notebooks, pipelines, tuning, and fair scheduling: a platform.

Why ML needs a platform: notebooks, pipelines, and experiment trackingguide coming
Kueue: queues, quotas, and fair sharing for training jobsguide coming
Argo Workflows: pipelines and batch orchestration on Kubernetesguide coming
Kubeflow in 2026: what it is now and when to use itguide coming
Model registries and versioning in practiceguide coming

โœ“ Checkpoint: you can now

Stand up a real ML platform: notebooks, pipelines, tuning, and batch scheduling with quotas.

โšก Prove it

Run one training pipeline end to end: train a small model, tune one hyperparameter, and version the result.

Serving & inference in production

~2-3 weeks

Training gets the glory; serving pays the bills. Put models behind reliable, scalable endpoints.

From laptop to cluster: what changes when serving moves to Kubernetesguide coming
vLLM on Kubernetes: production serving deep diveguide coming
KServe: standardized inference endpoints and when you need themguide coming
Scaling inference: autoscaling, caching, and cost per tokenguide coming

โœ“ Checkpoint: you can now

Serve a model behind a real endpoint and defend your runtime choice (vLLM, Triton, ONNX) like production teams do.

โšก Prove it

Deploy one model two ways: a standardized serving stack and a raw vLLM deployment; compare latency and ops burden.

LLMOps, AIOps & agents

~ongoing

Day 2: costs, observability, memory, and letting AI help run the infrastructure itself.

LLMOps: evals, prompt versioning, and safe rolloutsguide coming
RAG infrastructure: vector databases on Kubernetesguide coming
Model and drift monitoring in productionguide coming

โœ“ Checkpoint: you can now

Run models and agents in production with observability, cost control, and memory hygiene.

โšก Prove it

Put an agent behind a gateway, cap its spend, audit what it remembers, and let K8sGPT explain your next cluster incident.

Want to know when the ๐Ÿšง steps ship?

New articles, videos, and labs land in the newsletter first.

Get updates โ†’