In late 2024, customers demanded Kubernetes support on Oxide but lacked integrations. As Oxide's first Solutions Software Engineer, I tackled this challenge with customer feedback driving development. We built three integrations: Rancher Node Driver, Omni Infrastructure Provider, and Cluster API Provider (CAPOx).

Each emerged from real customer workflows—Rancher unblocked an existing pull request, Omni partnered with Sidero Labs for Kube Con 2025, and CAPOx addressed growing customer demand. The Oxide Cloud Controller Manager (CCM) ensures Kubernetes tracks Oxide instances accurately, reconciling infrastructure state. This customer-shaped approach uncovered gaps across provisioning, networking, and storage, guiding both integrations and platform improvements. Rancher Node Driver translated VM operations into Oxide API requests, while Omni Infrastructure Provider solved Talos Linux compatibility issues. CAPOx delivered Kubernetes-native cluster management, and the CCM maintains runtime synchronization between Kubernetes Nodes and Oxide instances.