I wanted Rancher to provision a Kubernetes cluster directly onto VergeOS — clone the VMs, install RKE2, hand me a Ready cluster, no manual node-building. VergeOS ships an integration for exactly this: a Rancher UI extension and a docker-machine node driver, installed from their Helm chart repo. Almost all of it
The silent deploy The task was unremarkable: spin up a new VM from a recipe, attach it to the management network, hand it back. I asked Claude to do it. It ran vrg recipe deploy ubuntu-base --set name=metrics-02, watched the task complete, and reported success. Exit code zero. Task
The result first $ curl -s --max-time 5 http://192.168.1.202/ | grep -o '<title>.*</title>' <title>VergeOS + Kubernetes: integration success</title> That hit a custom nginx pod on a single-node k3s cluster, through a LoadBalancer Service whose IP was
The locked room I had an admin tier I was happy about: a VergeOS internal network for the management VMs — the jump host, the box with vrg installed, the handful of internal tooling boxes you don't want anywhere near the public network. Outbound internet for package updates, but
If you run a VergeOS cluster, you’ve probably moved between three control surfaces: * The WebUI for clicking around * The REST API for scripting * The Terraform provider for declarative infrastructure The Verge.io team has now shipped a fourth option: vrg. But the important story is not simply “VergeOS has
new VergeOS related content is coming very soon.. stay tuned!