Lane 2 — Downstream

llm-d Content Plan

Net-new content focused on llm-d, tied back into Red Hat OpenShift. Every piece deployed on OpenShift, benchmarked on OpenShift, demonstrated on OpenShift.

Downstream Content Process

Four steps from draft to published, aligned with the AI BU and Inference pillar at every stage.

1

Create llm-d content with OpenShift tie-in

2

Align with AI BU & Inference pillar

3

Review in #forum-openshift-ai-serving

4

BU approves & publish

Existing llm-d Content

What already exists across Red Hat, the llm-d community, and third parties.

Red Hat Official

Community & Third Party

Content Gaps

What doesn't exist yet in the llm-d ecosystem. Each gap maps to a roadmap item below.

OpenShift Deployment

All deployment content is GKE or generic K8s. Zero OpenShift walkthroughs existed before ours.

Practitioner Benchmarks

All Red Hat articles are conceptual. Nobody had published "here's my cluster, here's what I measured."

Interactive Demo

Static blogs and videos only. No interactive tool for presenting llm-d concepts at conferences or in meetings.

Monitoring & Observability

No content on monitoring llm-d in production. Routing decisions, cache hit rates, GPU utilization dashboards.

Cost / ROI Analysis

Throughput numbers exist but nobody has mapped them to $/token or $/request savings for enterprise decision-makers.

Multi-Tenant Patterns

No content on serving multiple teams from shared GPU infrastructure with llm-d routing policies.

Office Hours Strategy

Build an audience for llm-d through existing vLLM sessions, then spin up dedicated office hours when traction justifies it.

Office Hours Rollout

Phase 1 — Starting July 2026

Every Other vLLM Office Hours = llm-d

Alternate existing vLLM office hours with llm-d sessions. Find speakers from engineering, community, and production users. Uses existing timeslot and audience.

Phase 2 — If It Takes Off

Dedicated llm-d Office Hours

If alternating sessions gain traction and there's enough speaker pipeline, spin llm-d into its own standalone office hours series.

Resources

What's available for content creation and demos.

H200 GPU Booking

demo.redhat.com → RHAI → GPU Booking. Book by day, 30-day window. For benchmarks, recordings, live demos.

LiteMaaS

demo.redhat.com → Model-as-a-Service. API access to hosted models (DeepSeek, Granite, Llama, Phi).

OpenShift Cluster

demo.redhat.com → AWS with OpenShift Open Environment. Fresh OpenShift 4 cluster on AWS.

GitHub Pages

Free static hosting for interactive sites and demo apps.

llm-d Slack

#sig-benchmarking channel for sharing results, getting feedback, finding collaborators.

r/llm_d

Small, engaged subreddit. Good for posting data and getting community visibility.

Content Roadmap

20 content pieces + ongoing micro-content & social media, June–December 2026

June 2026
1
Deploy llm-d on Kubernetes in 5 Minutes Complete
Video Blog

5-minute deployment walkthrough of llm-d on OpenShift with GPU. Video covers the full flow from zero to working inference routing. Blog submitted for editorial review.

Deployed on Red Hat OpenShift with GPU operator
POC → ProductionKubeCon · DevConf
Video: 5-minute screencast walkthrough. Screen recording of full deployment flow with casual voiceover — terminal on screen, no slides. Exported as YouTube upload + 60-second cut for LinkedIn/X.
2
47x Faster TTFT: Benchmarking llm-d Cache-Aware Routing on H200 GPUs Complete
Blog Interactive Web App Video

Data-driven benchmark of llm-d's KV-cache-aware routing vs round-robin on Llama 3.1 70B (FP8) across 3x H200 GPUs. 8 tests covering context scaling (500–32K tokens), concurrent load, agentic chains, and multi-turn conversations. Companion interactive web app visualizes results. Includes a “Cost Impact” tab translating TTFT and throughput gains into dollar savings — GPU-hours saved, cost-per-token reduction using real GPU pricing (H200, MI300X).

Key results: 47.5x TTFT improvement at 32K context, 75% TTFT reduction under 10-session concurrent load, 40% improvement in 12-step agentic chains. All measured in-pod to eliminate network variables.
Benchmarked on Red Hat OpenShift with 3x NVIDIA H200 141GB HBM3e GPUs
Cost Per Token · GPU EfficiencyRed Hat Summit · KubeCon
Video: 3-minute data walkthrough — screen recording of the interactive web app with voiceover narrating each benchmark result. Plus a 30-second social clip: one chart, one stat, one takeaway. YouTube + LinkedIn/X.
3
llm-d Interactive Conference Demo Complete
Web App

Interactive React app for conference showcases. Content adapts based on viewer's industry (17 sub-sectors across 7 categories) and role (5 levels from executive to platform engineer). 10 stages covering vertical optimization through expert parallelism, with animated architecture diagrams. Includes a “Decision-Maker Mode” — a shorter path that skips routing internals and focuses on business outcomes: “that cache hit saved X GPU-seconds.” Video tutorial walkthrough planned.

POC → Production · Conference DemoRed Hat Summit · KubeCon · DevConf
Video: 2-minute booth demo recording. Screen capture of the interactive demo being used at a conference — click through industries, watch architecture diagrams animate. Plus a 5-minute video tutorial walkthrough for YouTube. 30-second social cut of the Decision-Maker Mode path.
July 2026
4
How llm-d's Prefix-Cache-Aware Routing Works Complete
Blog Web App Video

Deep dive into the routing algorithm. How the EPP tracks KV cache state across replicas and scores routing decisions. Why multi-turn conversations and agentic workflows benefit the most.

Demonstrated with llm-d running on OpenShift, routing across OpenShift-managed pods
Core DifferentiatorKubeCon
Video: 3-minute animated explainer. Screen recording of the routing animation web app with voiceover walking through how the EPP scores and routes requests. 30-second social cut of one routing decision in action.
5
llm-d Monitoring & Observability on OpenShift Complete
Web App Video Blog

How to monitor llm-d inference workloads in production. Setting up dashboards for routing decisions, cache hit rates, GPU utilization, and latency. Ships a real Grafana dashboard.json on GitHub that people can import directly. The monitoring simulator web app becomes the companion guide.

Built on OpenShift monitoring stack: Prometheus, Grafana, alerts out of the box
Production ReadinessKubeCon · DevConf
Video: 5-minute setup walkthrough. Screen recording: import the dashboard.json, configure Prometheus scraping, walk through each panel. Practical “here’s what to watch” narration. 60-second social cut showing a live cache-hit spike on the dashboard.
12
The GPU Cost Cliff
Web App Blog Video

Interactive visualization of inference costs as concurrent users scale from 10 to 1,000. Real GPU pricing (NVIDIA H200, AMD MI300X). Terrain-style visualization: calm rolling hill with llm-d vs. exponential cliff face without it. Companion blog translates benchmark numbers into dollar savings. 30-second screen recording for social media.

Cost modeled on OpenShift GPU operator pricing with real cluster benchmark data
Cost Story · CFO ConversationRed Hat Summit · KubeCon
Video: 30-second social clip — drag the slider from 10 to 1,000 users, watch the cost cliff appear. No voiceover needed, just on-screen text: “This is what happens to your GPU bill.” Plus a 2-minute walkthrough version with narration for YouTube.
August 2026
6
Deploying llm-d with Disaggregated Prefill & Decode
Video Blog

Advanced deployment guide showing separate prefill and decode workers. How to split compute-bound and memory-bound phases for maximum throughput.

Deployed on OpenShift with separate node pools for prefill vs. decode workers
GPU Efficiency · ThroughputKubeCon
Video: 5-minute technical screencast. Terminal recording of deploying separate prefill and decode workers, then showing the throughput improvement in real time. Voiceover explains why splitting phases matters. YouTube.
13
“What Breaks at Scale” — Interactive POC-to-Production Walkthrough
Web App Blog

Start with a working single-node inference setup, then crank up the load. Watch things break — visually. Queue depth grows, latency spikes, cache misses cascade, pods crash. Then “install” llm-d components one by one and watch each problem resolve. Companion blog: “I Tried to Scale LLM Inference Without llm-d. Here’s Where It Broke.”

Failure scenarios modeled on real OpenShift deployment scaling patterns
POC → Production · 95% Fail StatKubeCon · Red Hat Summit
Video: 3-minute screen recording of the interactive walkthrough. Start stable, crank load, watch things break visually, then install llm-d components one by one. Satisfying “fix cascade” moment. 60-second social cut of the break-then-fix sequence.
14
“Who’s Building llm-d” — The Community Story
Blog Video

Profile the llm-d coalition from a community perspective. CoreWeave, Google Cloud, IBM, NVIDIA, AMD, Microsoft, Oracle — why each showed up, what they’re contributing, and what it signals about the project’s trajectory. Written as a community advocate, not a partner press release. Companion video: short interviews or commentary on what open-source collaboration at this scale looks like.

Red Hat’s open-source stewardship model: community-built, enterprise-delivered through OpenShift
Ecosystem · Partner CoalitionRed Hat Summit
Video: 3-minute community highlight. Talking head or voiceover with partner logos on screen. “Here’s who’s contributing to llm-d and why that matters.” Warm, community-advocate tone — not a press release. LinkedIn-first.
September 2026
7
Serving Multiple LoRA Adapters with llm-d
Video Blog

How to serve multiple fine-tuned models from a single base model using llm-d's LoRA-aware routing. Practical guide for teams running multiple specialized models.

Multi-adapter serving on OpenShift: one cluster, one base model, many adapters
Multi-Tenant · CostRed Hat Summit · DevConf
Video: 5-minute deployment walkthrough. Screen recording: deploy base model, add LoRA adapters, send requests to different adapters, watch routing in action. Terminal + browser side by side. YouTube.
8
llm-d for Multi-Tenant AI on OpenShift
Blog Architecture Guide

How enterprises serve multiple teams from shared GPU infrastructure using llm-d on OpenShift. Namespace isolation, per-team routing policies, quota management.

OpenShift multi-tenancy + llm-d routing: enterprise GPU sharing done right
Enterprise Cost · Multi-TenantRed Hat Summit
Video: No dedicated video — architecture guide format. Potential 2-minute animated diagram walkthrough showing namespace isolation and per-team routing if visual assets are available.
15
“Choose Your Own Inference Stack” — Architecture Decision Tool
Web App Config Generator

Interactive decision tree: answer 5 questions about your workload (model size, traffic pattern, hardware, latency requirements, multi-tenancy) and get a visual architecture diagram with a shareable deployment config. The kind of tool engineers bookmark and send to their team. Output includes Helm values and recommended llm-d settings.

Generated configs target OpenShift with Helm charts, GPU operator, and monitoring pre-configured
Vendor Lock-in Avoidance · Hardware FlexibilityKubeCon
Video: 2-minute screen recording of the config generator in action. Answer 5 questions, watch the architecture diagram build itself, download the config. 30-second social cut of the diagram animation. The “build your own” moment.
October 2026
9
llm-d at Scale: Lessons from Production
Blog Case Study

Real-world deployment patterns with llm-d. Scaling from 2 GPUs to 100+. Operational lessons, monitoring, and what to watch for.

Scaled on OpenShift: cluster autoscaling, GPU scheduling, production operations
POC → ProductionRed Hat Summit
Video: 8–10 minute deep dive. Talking head or voiceover with production dashboards on screen. Walk through real scaling decisions, failure modes encountered, and what the monitoring showed. The “war stories” format — candid, not polished. YouTube.
16
Agentic Demand Visualizer — Why Agents Need llm-d
Web App Blog Video

Visualize what an AI agent’s inference pattern looks like over time — bursty, multi-turn, tool-calling, context-switching. Show how naive round-robin routing handles it (cold starts everywhere, cache thrashing) vs. how llm-d routes it (sticky sessions, prefix cache hits). Air-traffic-control aesthetic. Companion blog: “I Built an AI Agent. Here’s the Inference Bill.” 2–3 minute video walkthrough.

Inference patterns captured from real agent workloads on OpenShift AI with Llama Stack
Agentic AI InfrastructureKubeCon · Red Hat Summit
Video: 2–3 minute walkthrough of the visualizer. Show bursty agent traffic, watch routing decisions in real time, compare naive vs. llm-d side by side. Air-traffic-control aesthetic makes great social content. 30-second social cut of the side-by-side comparison.
20
From llm-d to Red Hat AI Inference Server
Blog Web App Video

How the open-source llm-d project becomes the Red Hat AI Inference Server inside Red Hat AI 3. Architecture mapping: what’s upstream, what’s packaged, what Red Hat adds (support, FIPS, lifecycle). The piece that connects community contributors to enterprise buyers — “the code you wrote is now running in production at [Fortune 500].”

Core component of Red Hat AI 3 — enterprise packaging, support, and certification on OpenShift
Vendor Lock-in Avoidance · Enterprise BridgeRed Hat Summit · KubeCon
Video: 5-minute explainer. Animated diagram or slide-style walkthrough: open-source project → enterprise product pipeline. What stays upstream, what gets packaged, what Red Hat adds. Talking head segments optional. YouTube + conference use.
November 2026
10
llm-d + OpenShift AI: Enterprise LLM Serving
Video Blog

How llm-d fits into the broader OpenShift AI platform. The full picture from model training to llm-d serving. Product updates and the integrated experience.

The full Red Hat OpenShift AI + llm-d integration story
Platform IntegrationRed Hat Summit
Video: 5-minute integration demo. Screen recording showing the full OpenShift AI + llm-d experience: model registry, deploy, route, monitor. End-to-end platform story with voiceover. YouTube + conference playback.
17
“Inference Under the Hood” — The Transparent Cluster
Web App

Visual cluster sandbox: see pods, send inference requests, watch the EPP route them in real time, see KV cache state update, watch responses stream back. Users send their own prompts. The booth demo that makes people crowd around. Evolved from the interactive demo into a live, explorable infrastructure visualization.

Pod topology and routing visualization mirrors real OpenShift cluster state
Booth Demo · Conference MagnetRed Hat Summit · KubeCon · DevConf
Video: 2-minute screen recording of the cluster sandbox. Send a prompt, watch the EPP route it, see KV cache light up, response streams back. Mesmerizing “watch the infrastructure think” moment. 30-second social cut of one request lifecycle. Booth loop video at conferences.
18
llm-d Deployment Starter Kit
GitHub Repo Blog

Open-source repo: Helm charts, deployment configs, and recommended settings for 3 scenarios (single-model serving, multi-model routing, agentic workloads). The “Deploy in 5 Minutes” blog becomes the README. Not just content — a tool that generates its own content through community adoption and contributions.

OpenShift-native deployment templates with GPU operator and monitoring pre-configured
POC → Production · CommunityKubeCon
Video: 10-minute hands-on tutorial. Terminal recording: clone repo, pick a scenario, deploy with Helm, verify it works. The video version of the README. Practical, no fluff. YouTube.
December 2026
11
2026 Year in Review: The State of Open Source LLM Inference
Blog Infographic

Landscape overview of where open-source LLM inference stands. Where llm-d fits, community growth, Red Hat's role in the ecosystem, and what's coming in 2027.

Red Hat's role in open-source inference: llm-d, vLLM, and the OpenShift platform
Ecosystem · CommunityAll Events
Video: 3-minute highlight reel. Montage of the year’s best moments: benchmark results, community milestones, conference demos, partner announcements. Upbeat music, on-screen stats, quick cuts. LinkedIn + YouTube year-end post.
19
llm-d Routing Deep Dive — Interactive Technical Paper
Web — Distill-style Blog

Distill.pub-style long-form technical explainer of llm-d’s routing algorithm with interactive inline figures. Scroll and diagrams animate, charts respond to input. Elevates the prefix-cache routing content to a format engineers share because it’s beautiful and educational. The “I can’t believe someone made this” piece.

Architecture diagrams show OpenShift-native deployment topology and pod routing
Technical DifferentiatorKubeCon
Video: 3-minute scroll-through recording. Screen capture of someone scrolling the interactive paper — diagrams animate, charts respond. Voiceover highlights key insights. The “I can’t believe someone made this” social share. LinkedIn-first.

Ongoing Micro-Content

Content that runs on a cadence, not a calendar date. Low effort, high reach.

Video Micro-Content

  • Weekly 30-Second Screen Recordings
    Record your screen using an existing web app for 30 seconds with casual voiceover. Post on LinkedIn and X. No intro, no outro, no music. One per week from a different app. Highest ROI play — assets already exist, just capture moments.
  • “Watch This Cache Hit” — 15-Second Clip
    Send a prompt. See it route. Send the same prompt. Watch it hit cache and come back 47x faster. Just the visual with a subtitle. Satisfying like factory videos people can’t stop watching.
  • “60 Seconds of llm-d” — Personal Elevator Pitch
    You, talking to camera or voice over a demo, explaining why llm-d matters in 60 seconds. One take. Unpolished is what makes it credible. LinkedIn pinned post, email signature link, the thing you text when someone asks “what do you work on?”
  • Live Benchmark Race — Conference Event
    At a conference: two identical clusters, same model, same prompts. One with naive routing, one with llm-d. Race them live on a screen. People gather around races. Film it for social media afterward.

Other Recurring

  • Conference Talk Reframes
    New CFP abstracts for existing demos, pitched through the strategic lens. Instead of “How cache-aware routing works” → “Why 95% of AI projects die at inference — and how to be the 5%.” Same demos underneath, different framing.
  • “llm-d Explained Simply” — Non-Technical Analogy
    Blog post or short video explaining llm-d using an analogy anyone can understand. Airport gate routing. Restaurant kitchen management. Highway traffic flow. No jargon. Hardest thing to do well, most shareable thing you’ll ever make.
  • “llm-d vs. the Field” — Honest Comparison Blog
    Candid blog: “Here’s what TensorRT-LLM does better. Here’s where SGLang shines. Here’s where llm-d wins. Here’s what we’re still working on.” Radical honesty is the most impressive thing a developer advocate can do.

Social Media Content Kit

Ready-to-post content for LinkedIn and X. Adapt the voice, keep the substance. Same verbiage works across similar platforms.

Templates by Content Type

Web App Launch

I built [thing]. [One-sentence hook about what it does]. Try it → [link]

[2–3 sentences about why this matters]

#llmd #opensource #inference

Benchmark / Data

[Stat]. That’s what we measured with [method]. Not theoretical — real [hardware], real [workload], real results.

Data → [link]

#llmd #inference #benchmarks

Short Video

[X] seconds. That’s all it takes to see [thing]. Watch:

[video]

#llmd #inference

Community / Ecosystem

[Company names]. All contributing to the same open-source inference project.

[Why this matters]

[link]

#llmd #opensource #community

Ready-to-Post: Existing Content

Benchmark #2 — 47x Faster TTFT
LinkedIn
47.5x faster time-to-first-token.

That’s what we measured running Llama 3.1 70B on 3x H200 GPUs with llm-d’s cache-aware routing vs. round-robin. Not a synthetic benchmark — real requests hitting a real cluster.

Interactive results → [link]

#llmd #inference #benchmarks #opensource
X
47.5x faster TTFT. Real H200 GPUs, real requests, llm-d cache-aware routing vs round-robin. Interactive results → [link] #llmd
Web App #3 — Interactive Conference Demo
LinkedIn
Need to explain llm-d at a conference in 2 minutes?

I built an interactive walkthrough that adapts to your audience’s industry and role. 10 stages from vertical optimization to expert parallelism, all with animated architecture diagrams.

Try it → [link]

#llmd #conferences #opensource #devrel
X
Explain llm-d in 2 minutes. Interactive demo that adapts to your audience’s industry and role. 10 stages, animated diagrams. → [link] #llmd
Video “Watch This Cache Hit” — 15-Second Clip
LinkedIn
15 seconds.

Watch the first request route to a pod. Then watch the second request hit the KV prefix cache and come back 47x faster.

That’s what cache-aware routing does.

[video]

#llmd #inference #opensource
X
Cache miss → cache hit → 47x faster. 15 seconds. [video] #llmd

Ready-to-Post: New Content

Web App #12 — The GPU Cost Cliff
LinkedIn
What happens to your inference costs when you go from 10 to 1,000 concurrent users?

I built an interactive visualization with real GPU pricing. Drag the slider and watch the cost curve. With naive routing, it’s a cliff. With llm-d’s cache-aware routing, it’s a hill.

Try it → [link]

#llmd #inference #GPU #opensource
X
Drag the slider from 10 to 1,000 concurrent users. Watch your GPU costs either cliff or hold steady. The difference is cache-aware routing. → [link] #llmd #inference
Web App #13 — What Breaks at Scale
LinkedIn
I started with 1 GPU running inference. Then I cranked it to 50.

Here’s exactly where it broke — cold starts, cache misses, routing chaos, latency walls. Built an interactive walkthrough where you watch it happen, then fix each problem by adding llm-d components one by one.

→ [link]

#llmd #inference #scaling #opensource
X
1 GPU to 50. Here’s where inference breaks — and how to fix each failure. Interactive walkthrough → [link] #llmd
Blog #14 — Who’s Building llm-d
LinkedIn
CoreWeave. Google Cloud. IBM. NVIDIA. AMD. Microsoft. Oracle. Cisco. Hugging Face.

All contributing to the same open-source inference framework.

Here’s the story of how the llm-d community came together — and what it means for the future of LLM serving.

→ [link]

#llmd #opensource #AI #community
X
9 companies. 1 open-source inference framework. Here’s how the llm-d community came together → [link] #llmd #opensource
Web App #16 — Agentic Demand Visualizer
LinkedIn
A 30-second AI agent conversation generated 47 inference requests across 3 models.

I built a visualizer that shows what agent workloads actually look like under the hood — and why they need smarter inference routing than round-robin can provide.

→ [link]

#llmd #agents #inference #opensource
X
30 seconds of agent conversation = 47 inference requests. This is why agents need smarter routing. → [link] #llmd #agents
Web App #15 — Choose Your Own Inference Stack
LinkedIn
Answer 5 questions about your workload. Get back a deployment architecture and config.

Built a decision tool for llm-d: model size, traffic pattern, hardware, latency needs, multi-tenancy. It generates a visual architecture diagram and a shareable config you can actually use.

→ [link]

#llmd #kubernetes #inference #devtools
X
5 questions about your workload → a deployment architecture and config for llm-d. Try it → [link] #llmd #k8s
Video “60 Seconds of llm-d” — Elevator Pitch
LinkedIn
Enterprises are spending billions on GPUs for AI inference and wasting 40–60% of that compute.

llm-d is an open-source Kubernetes-native framework that makes LLM inference distributed, cache-aware, and hardware-agnostic. It runs on NVIDIA, AMD, Intel — no vendor lock-in. It’s backed by CoreWeave, Google, IBM, NVIDIA, and a dozen more.

60 seconds. Here’s what it does and why it matters.

[video]

#llmd #inference #opensource
X
Enterprises waste 40–60% of GPU compute on inference. llm-d fixes that — open-source, Kubernetes-native, runs on any hardware. 60 seconds on why it matters. [video] #llmd