
About This Playground
Want to try a kubectl command, deploy an application, or explore an alternative lightweight Kubernetes distribution without installing anything locally?
iximiuz Labs' k0s playground gives you a ready-to-use, single-node Kubernetes cluster running on a fresh Linux server. The VM starts in seconds, opens in your browser, and acts as both the Kubernetes control plane and the worker node—making it a compact environment for experimentation, development, and learning.
This is not a simulated or containerized Kubernetes environment. The cluster runs inside a lightweight but fully fledged VM on iximiuz Labs' bare-metal infrastructure. The machine has its own kernel and root filesystem, and k0s runs directly on it, much like it would on a VPS, an edge device, or a server in your homelab.
k0s is a lightweight, CNCF-certified Kubernetes distribution packaged as a single binary with almost no host-level dependencies. Underneath, you still get the familiar Kubernetes API and core abstractions, so regular manifests, controllers, and troubleshooting techniques work as expected.
Use the k0s playground to learn Kubernetes fundamentals, test manifests and operators, inspect how k0s assembles and manages a cluster, or compare it with distributions such as K3s and kubeadm. Its single-node shape also makes it a convenient sandbox for small applications, controllers, API experiments, and short-lived demos.
This is a single-node cluster, so it cannot reproduce multi-node scheduling, node failures, or other distributed scenarios. For those experiments, use one of the multi-node Kubernetes playgrounds instead. As with all iximiuz Labs playgrounds, it is not intended for production workloads or services that must stay online indefinitely.
For everything else, start the cluster and get your hands dirty. The fastest way to understand a Kubernetes distribution is to deploy a few workloads, inspect the processes and configuration underneath, break something, and learn how to put it back together.
Happy hacking!
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs →
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs →
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs →
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs →
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs →
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs →
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs →
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs →
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs →