Oxide Computer Bridges Private Cloud Gap With Kubernetes Integration

Oxide Computer has released a Cloud Controller Manager (CCM) that enables customers to deploy Kubernetes directly onto its private cloud infrastructure. The move allows the industry-standard orchestrator to interface with Oxide's proprietary API-driven hardware primitives.

To achieve this integration, Oxide implemented the CCM to bridge Kubernetes extension points with the company's infrastructure APIs. A primary focus of the initial release is the functionality of 'LoadBalancer' services. Because a native load balancer is not yet available, Oxide is utilizing floating IPs to translate destination addresses to a node's internal IP. According to Oxide Computer, the current implementation publishes both the floating IP, referred to as Proxy mode, and the node's internal IP, known as VIP mode, within the Service status. Additionally, the integration supports 'externalTrafficPolicy: Cluster,' which ensures traffic can be forwarded to any endpoint across the cluster.

The Private Cloud Challenge

Oxide Computer provides the Oxide Cloud Computer, a vertically integrated data center rack designed to function as a private cloud. While the company had already established the necessary hardware and API foundations, it lacked the specific software integrations required for seamless deployment of standard orchestration tools. For many enterprise users, the ability to use Kubernetes is a prerequisite for adopting new infrastructure, as it prevents vendor lock-in and allows for the use of existing deployment manifests.

Industry Implications

This integration is a critical step for Oxide's enterprise adoption strategy. By building a greenfield CCM, Oxide can offer a "cloud-like" experience on dedicated private hardware. This allows users to maintain standard Kubernetes workflows—such as defining LoadBalancer services—while the underlying physical infrastructure continues to evolve. It effectively removes a significant friction point for organizations that want the control of a private rack with the operational flexibility of a public cloud provider.

Future Outlook

While the current floating IP system provides a functional workaround for traffic management, the long-term goal remains the development of native infrastructure services. Observers will be watching to see when Oxide replaces these proxy mechanisms with a native load balancing solution. For now, the CCM provides the necessary bridge for early adopters to migrate their containerized workloads to Oxide's integrated hardware environment.