FAQ Friday

And I like to group these into three different categories: integrations to create a cluster, to manage a cluster, and to use a cluster.

To create a cluster, we have integrations with SUSE Rancher and Sidero Labs Omni. We have a Rancher node driver that allows you to use SUSE Rancher to spin up instances on Oxide and form Kubernetes clusters. And you can scale those instances up and down and manage the Kubernetes cluster via Rancher. We also have a Sidero Labs Omni infrastructure provider that allows you to dynamically spin up and down Oxide instances running Talos Linux and connect them to Omni to manage your Kubernetes clusters with Sidero Labs' Omni product.

For managing your cluster, we have the Oxide cloud controller manager. And the cloud controller manager component, it’s a component in Kubernetes that allows you to integrate Kubernetes with the underlying cloud provider API. In this case, Oxide. And our cloud controller manager allows you to manage node health and soon service controllers to manage your services of type load balancer.

To use your cluster, we have a CSI plugin under active development where you can use Oxide storage for your persistent volume claims.

Now I’ve demoed all of these integrations over the past couple of weeks at KubeCon, at Cloud Field Day, on a Sidero webinar, and All Things Open. So there’s plenty of resources out there for you to go see how these integrations work.

And if you need more written information, we have RFD 493 and RFD 595 for you to get more information. And if that’s still not enough, reach out to me. I’d love to chat about your Kubernetes workloads and see how we can run them on Oxide because Oxide is rapidly becoming a great platform to run your Kubernetes workloads. And I’m here to make sure that happens, right, to develop these integrations, to make sure that you’re successful running Kubernetes on Oxide. Thanks.