docs: Clean up incomplete recipes and clarify Kubernetes-only focus #4145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Objective
Clean up the
recipes/directory to focus exclusively on production-ready Kubernetes deployments for release 0.6.1. Remove incomplete configurations and clarify that benchmark recipes are tools for users, not published performance results.📊 Summary of Changes
34 files changed: +210 insertions, -1,542 deletions
Deleted Content
5 incomplete model directories (no K8s
deploy.yamlmanifests):deepseek-r1-distill-llama-8b/gemma3/llama4/qwen2-vl-7b-instruct/qwen3/(keptqwen3-32b-fp8/which is complete)run.shscript (228 lines) - non-K8s automation tool12 standalone engine config YAMLs from
deepseek-r1/trtllm/:agg/simple/,agg/mtp/,agg/wide_ep/(all subdirs)disagg/simple/,disagg/mtp/disagg/wide_ep/*.yaml(standalone configs only)disagg/wide_ep/gb200/(has complete K8s manifests)Added/Modified Content
Comprehensive new
recipes/README.mdwith:gpt-oss-120b/trtllm/disagg/README.md- Documents incomplete recipe status📦 What Remains
4 Models | 10 Complete Deployments | 7 with Benchmark Recipes
🔑 Key Changes Explained
1. Removed Incomplete Model Directories
Issue: 5 model directories contained only standalone engine configs (
.yamlfiles) without Kubernetesdeploy.yamlmanifests. These were added in PR #3772 but don't follow the documented recipe structure.Resolution: Remove them from 0.6.1. Can be re-added properly in 0.7.0 with complete K8s manifests.
2. Removed
run.shScriptIssue: Automated deployment script for non-K8s environments. Adds complexity and isn't aligned with K8s-only focus.
Resolution: Remove for 0.6.1. Recipes directory should contain declarative K8s manifests only.
3. Cleaned Up Standalone Engine Configs
Issue:
deepseek-r1/trtllm/contained many standalone engine config YAMLs (agg.yaml,decode.yaml,prefill.yaml) that aren't wrapped in K8s manifests. These configs are meant to be embedded as ConfigMaps withindeploy.yamlfiles.Resolution: Remove standalone configs. The one complete recipe (
disagg/wide_ep/gb200/deploy.yaml) already embeds its configs as ConfigMaps.4. Clarified "Benchmark Recipe" vs "Benchmarked"
Issue: Previous README implied we have published benchmark results. We actually provide benchmark tools (
perf.yamlwith AIPerf).Resolution:
perf.yamlfor running AIPerf benchmarks"📁 Directory Structure (After)
🤔 Review Focus Areas