User-defined Playground

DEV: Architect Playground

Scale Kubernetes to Zero, Wake it up Instantly

DEV: Architect playground: Scale Kubernetes to Zero, Wake it up Instantly
Machines & network
5 VMs ยท 10 vCPU ยท 15GiB RAM
Playground host Internet NAT MASQUERADE local (bridge) 172.16.0.0/24 gw 172.16.0.1/24eth0eth0eth0eth0eth0
VM
vCPU ยท
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/base/kubeadm-cluster/dev-machine:e3eaa8490eea
VM
vCPU ยท
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/base/kubeadm-cluster/control-plane-defaults:4a5298b7a0ae
VM
vCPU ยท
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/base/kubeadm-cluster/worker-defaults:ae9220ad78ad
VM
vCPU ยท
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/base/kubeadm-cluster/worker-defaults:ae9220ad78ad
VM
vCPU ยท
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/base/kubeadm-cluster/worker-defaults:ae9220ad78ad
About

This playground gives you a four-node Kubernetes cluster with Architect installed. Use it to see how Architect hibernates idle workloads and wakes them on demand without deleting the Pods first.

๐Ÿ”‘ Get a Token

This playground installs Architect during startup. When the launch form asks for Machine token and Cluster name, get them from the Architect Console first.

  1. Open console.architect.io and create an account if needed.
  2. Click Install Architect on your Kubernetes cluster.
  3. Choose Generic.
  4. Pick a cluster name.
  5. Click Next on the labels page. This playground labels the nodes for you.
  6. On the last page, copy the machine token and the cluster name into the playground start form.
Important

โฐ It takes 2-3 minutes for the playground to boot.

Note

๐Ÿ’ก No need to copy the Helm command from the console. This playground installs Architect automatically during initialization.

Screenshots

๐Ÿ”ง System Components

MachineRole
dev-machineWorkstation with kubectl access to the cluster
control-planeKubernetes control plane and stable node for Architect control components
worker-01Worker node managed by architectd
worker-02Worker node managed by architectd
worker-03Worker node managed by architectd

Architect is installed during playground startup using the machine token and cluster name you provide when launching the environment.

๐ŸŽฏ Getting Started

Once the playground is running, open the dev-machine terminal. It is already configured with kubectl access to the cluster.

Verify that the Kubernetes nodes are ready:

kubectl get nodes

Then check that the Architect components are running:

kubectl get pods -n architect -o wide
kubectl get runtimeclass

You should see Architect control plane components in the architect namespace and the runc-architect runtime class.

๐Ÿงช Example

Important

TODO: Add link to Valkey tutorial

๐Ÿ“š Learn More

Happy learning! ๐Ÿš€

Every playground includes
Learn more about playgrounds
Start
Settings