What is vCluster?
vCluster is an open source way to run virtual Kubernetes clusters inside an existing (host) Kubernetes cluster giving teams their own Kubernetes API server and environment without needing to spin up a full new physical cluster for every team or workload. It’s commonly used for platform engineering, multi-tenancy, CI/CD, dev/test environments, and isolated workloads. (vcluster.com) It covers the entire tenancy spectrum where it supports different tenancy modes that you can read more about here.
Introducing the first vCluster Ambassadors
Today we’re announcing the first cohort of the vCluster Ambassador Program.
These are builders and community leaders who have already been showing up consistently — teaching, sharing, shipping, and helping others adopt better Kubernetes practices. In many ways, they were ambassadors before we created the program.
Please welcome our first vCluster Ambassadors:
Over the next few days, we’ll post individual spotlights for each ambassador (what they work on, what they’re excited about, and what they’re building with vCluster).
What is the vCluster Ambassador Program?
The vCluster Ambassador Program is a way to recognize and support community leaders who:
- educate others (talks, content, workshops),
- share real-world practitioner feedback,
- help more teams adopt vCluster in practical, repeatable ways.
Why we’re doing this (and why now)
vCluster sits at the center of some of the most important shifts happening in Kubernetes right now:
- multi-tenancy beyond namespaces
- platform teams needing isolated environments at scale
- faster dev/test/preview environments
- cost + efficiency pressures (especially when infra and AI workloads grow)
But here’s the truth: the best product decisions don’t come from assumptions — they come from the field. Therefore this ambassador program is our commitment to staying deeply connected to:
- what practitioners are actually doing,
- what’s working,
- what’s painful,
- and what we should build next.
This is a two-way bridge:
- ambassadors help the community learn faster,
- and they help us keep vCluster grounded in reality.
What ambassadors get (benefits)
We want ambassadors to feel supported, not “used for marketing.”
Benefits typically include:
- Recognition as an official vCluster Ambassador (badge, listing, spotlight posts)
- Direct access to the vCluster team for feedback + roadmap discussions (a real feedback loop)
- Early previews / briefings on upcoming releases and features (so you can build + teach earlier)
- Swag + perks (because community work deserves appreciation)
- Support for community work (where possible: Monetary support for talks/meetups/workshops, and content amplification, etc.)
A community of peers — other ambassadors they can collaborate with and learn from
What we expect (responsibilities)
This is not a “title.” It’s a great responsibility to our entire ecosystem.
Ambassadors are are leaders who:
- Teach and enable the community through talks, content, workshops, demos, and mentoring
- Create real-world learning material (blogs/videos/tutorials/examples) that helps teams adopt vCluster
- Share feedback on what’s confusing, what’s missing, what should be improved
Are constructive, professional, and community-first, ambassadors value honesty and they do it respectfully
Who should apply?
We’re opening applications for the next set of ambassadors.
You should apply if you’re doing 2–3 of these already (or you’re ready to start) on vCluster topics:
- speaking at meetups / conferences
- writing blogs / making videos
- running workshops / trainings
- contributing to OSS or building strong technical examples
- mentoring others in vCluster/Kubernetes/platform engineering
- actively using vCluster or exploring it deeply
You do not need a massive following. We care about:
- proof of work
- clarity of thinking
- consistency
- and genuine intent to help others.
How to apply
👉 Apply here: Application link
👉 Program page: Program link
When you apply, include:
- 2–5 links to your best work (talks, blogs, videos, repos, or workshops)
- what you want to focus on (multi-tenancy, AI Infrastructure, platform engineering, CI/CD, etc.)
- how you’d like to contribute in the next 3–6 months
If you’ve been contributing quietly, this is your nudge to apply.And if you know someone who fits, let them know.
Welcome again to our first vCluster Ambassadors — we’re excited to build the next chapter of Kubernetes tenancy and platform engineering with you. 💙
Deploy your first virtual cluster today.

