Kubernetes as a Service
A released managed Kubernetes service on VNETWORK's Cloud Compute Infra — a Go service that provisions real clusters and owns their full lifecycle on a Hosted Control Plane architecture. My role: base architect, mentoring the team's Rails → Go refactor.
Why
Offer Kubernetes-as-a-Service on VNETWORK’s in-house Cloud Compute Infra, replacing a Rails monolith with a purpose-built Go service — and use the rewrite to level up the team on Go.
What it does
Stands up real clusters: provisions VMs, installs Kubernetes, then owns the
full lifecycle — scale, version upgrades, snapshots, addons and deletion. It
also serves each cluster’s automated clients — cluster-autoscaler,
cloud-controller-manager and a CSI driver for dynamic volume provisioning
— through a dedicated API tier.
Architecture: Hosted Control Plane
Masters and workers are private-only VMs — no public IP, no internet. Each cluster’s control-plane entry is hosted on a dedicated node that fronts the apiserver, etcd and konnectivity through HAProxy, and also holds the PKI and acts as the jump host. Cluster operations flow through that hosted control plane.
- Scripts are pulled from the service API and read their context at runtime — nodes aren’t configured by hand.
- Progress advances by callback: nodes report each completed step, with a watchdog as a safety net.
- Version = image — upgrading means replacing nodes with a new image rather than upgrading in place.
My contribution
Two roles. As base architect for the service, I owned the design above — the Hosted Control Plane, the private-only node model, the runtime-pulled scripts, the callback-driven progress with its watchdog, and the version-as-image lifecycle. As mentor for the organization’s Rails → Go refactor, I led the team through the rewrite that replaced the Rails monolith with the Go service, using the migration itself to level the team up on Go.
Status
Released as a service.