Kind Cluster: OIDC AuthN Playground
A playground to demonstrate access control through OIDC authentication for Kubernetes.
- eth0
- /
- docker
Getting started
Find full detailed instructions for the playground at my blog https://diaz.bearblog.dev
Technologies used:
- kind
- auth0's free development instance for OAuth 2.0/OIDC and user management
- kube-apiserver with OIDC flags
- automation to mint ID tokens, configure kubeconfig, and grant K8s RBAC.
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 →