Skip to content

[v0.34] docs(ai-cloud): add ClusterMAX reference to production path intro (#2274) #2275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
djwfyi merged 2 commits into from
Jun 11, 2026
Merged

[v0.34] docs(ai-cloud): add ClusterMAX reference to production path intro (#2274) #2275

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
08ee7aa
Backport: Copy vcluster/production-guide/ai-cloud.mdx to vcluster_ver…
loft-bot Jun 11, 2026
209d072
Backport: Copy vcluster/production-guide/distributed-compute.mdx to v…
loft-bot Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion vcluster_versioned_docs/version-0.34.0/production-guide/ai-cloud.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Run a managed Kubernetes service on your GPU infrastructure. Each customer gets
<figcaption>Central control plane managing tenant clusters for customers</figcaption>
</figure>

**What makes this path different:** Customers never touch Platform. They interact with your product. Platform RBAC locks direct access to your platform engineering team.
**What makes this path different:** Customers never touch Platform. They interact with your product. Platform RBAC locks direct access to your platform engineering team. This architecture also maps to the cluster-level isolation criteria that AI cloud buyers evaluate in frameworks like [ClusterMAX](https://www.vcluster.com/clustermax).

@github-actions github-actions Bot Jun 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Google.WordList] Use 'tap' instead of 'touch'.


## Day 0: Design decisions

Expand Down
2 changes: 1 addition & 1 deletion vcluster_versioned_docs/version-0.34.0/production-guide/distributed-compute.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ One management plane for GPU compute from every source you own or contract. Whet
<figcaption>Central control plane managing tenant workloads across distributed compute capacity sources</figcaption>
</figure>

**What makes this path different:** Every compute source, regardless of where it lives or who operates it, follows the same onboarding playbook. One ops team, one management plane, no per-provider tooling.
**What makes this path different:** Every compute source, regardless of where it lives or who operates it, follows the same onboarding playbook. One ops team, one management plane, no per-provider tooling. This architecture also maps to the cluster-level isolation criteria that AI cloud buyers evaluate in frameworks like [ClusterMAX](https://www.vcluster.com/clustermax).

## Day 0: Design decisions

Expand Down
Loading