Skip to content

Add blog post: give each customer their own GPU with KubeVirt - #275

Draft
shkatara wants to merge 6 commits into
mainfrom
blog/gpu-per-customer-kubevirt-rke2
Draft

shkatara wants to merge 6 commits into
mainfrom
blog/gpu-per-customer-kubevirt-rke2

Conversation

@shkatara

@shkatara shkatara commented Oct 6, 2026

Copy link
Copy Markdown
Collaborator

Adds a runbook for passing one NVIDIA L4 through to a KubeVirt VM, then running RKE2, the NVIDIA GPU Operator and HAMi inside the guest.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Deploying website with  Cloudflare Pages  Cloudflare Pages

Latest commit: e6dd041
Status: ✅  Deploy successful!
Preview URL: https://38ddb882.website-dab.pages.dev
Branch Preview URL: https://blog-gpu-per-customer-kubevi.website-dab.pages.dev

View logs

shkatara and others added 5 commits October 9, 2026 21:54
Reframe the post around a platform team's GPU catalog. Both L4 cards go
to KubeVirt, one per VM: tenant-1 is a plain GPU VM running Ollama,
tenant-2 runs its own RKE2 with the GPU Operator and HAMi. Rename the
slug to ai-infrastructure-for-platform-engineers and regenerate the
routing artifacts.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Remove prompts from runnable blocks, keep them only where output is shown,
split mixed blocks, fix the tenant SSH commands and the starting-point text.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant