Your own namespace
tenant-<you> with full edit rights — deploy Deployments, Services, ConfigMaps,
Secrets, PVCs. Other tenants and the cluster internals are off-limits.
When you’re onboarded, you get your own namespace on the cluster — a private sandbox where you can run containers. You can deploy, scale, and tear down workloads freely inside it, but you can’t see or touch anyone else’s. Everything is reachable privately over Tailscale; nothing is exposed to the public internet unless you explicitly publish it.
Your own namespace
tenant-<you> with full edit rights — deploy Deployments, Services, ConfigMaps,
Secrets, PVCs. Other tenants and the cluster internals are off-limits.
Private by default
Reach the cluster over Tailscale, log in with your Google account. No VPN configs, no passwords, nothing on the public internet.
Strong isolation
Your pods run in lightweight VMs (Kata Containers), so even a container breakout stays trapped — it can’t reach the host or other tenants.
Public URLs on request
Want your app reachable from the web? It can get a *.dubnubdubnub.com URL with automatic
HTTPS — see Make an app public.
~/.kube/.kubectl + kubelogin, run a command, log in with Google.Full walkthrough → Connect to the cluster.