Oxide 自研 Kubernetes 集成方案
推荐指数 58.0 NO. 017 · 2026.08.14
发布2026/08/13Score99Comments38
为什么值得看
Oxide 从客户实际需求出发，从零构建了 Kubernetes 的 CSI、CAPI 等核心集成组件，而非简单包装上游工具。对运行私有云 K8s 的团队有参考价值——硬件厂商亲自下场做云原生集成仍是少数。
编辑判断
Oxide 选择自研而非 fork 或包装现有 provider，这个决策本身比技术细节更值得注意。大多数裸金属云厂商（如 Equinix Metal、Packet 时代）的做法是维护一个半死的 Cluster API provider，社区贡献稀薄，最终成为技术债。
Oxide 的 CSI 驱动直接对接其特有的磁盘快照和回滚 API，这是公有云 CSI 无法复用的差异化能力。如果你在评估类似 Nutanix、VMware 替代方案时的 K8s 兼容性，需要重点看厂商是否真正维护了完整的 CAPI + CSI + CCM 三条线，而非只提供一个能启动节点的最低可用版本。
另一个信号是 Oxide 设立 Solutions Software Engineer 这个岗位——硬件公司开始雇佣专职的"客户成功工程师"写代码，说明其商业模式从卖盒子转向卖可持续运行的平台。
社区反馈
正面 42 条评论
核心争论：Oxide 云原生集成路线获认可，社区关注 CCM 差异化设计与 Karpenter/CAPI 边界
相关内容
Kubernetes Overview / Guides / Oxide Oxide 维护 Cluster API、Omni 和 Rancher 三种 Kubernetes 集成方案，均支持通过 Oxide API 自动化管理实例生命周期。 cluster-api-provider-oxide/README.md CAPOx 是 Oxide 的 Cluster API 基础设施提供商，支持在 Oxide 云上声明式地创建和管理 Kubernetes 集群。 Where are we going with Oxide Computer Integrations? Matthew Sanabria 介绍 Oxide 未来集成方向，包括 Kubernetes CSI 存储插件和 Cluster API 支持。
I'm interested to see how the `oxide-cloud-controller-manager` is being built for "modern" Kubernetes and if it leads to any signify difference compared to CCMs that originated in-tree. Given the way Oxide engineer their solutions this could be really interesting. FYI I've got `karpenter-provider-ox
Yes this would be great addition! Also it would be awesome to see proper load balancer, ingress controller with `gateway api` and a `api gateway` (two separate things). I’m not an oxide customer, just a fan. I have lots of ideas around how something like this should look, being disappointed with the
I'll need to record a video on what's possible today. My personal Kubernetes cluster running on Oxide uses the CCM for LoadBalancer services and NGINX Gateway Fabric for Gateway API things. I'm mostly using HTTPRoute resources today. There's an opportunity to more tightly integrate at the network la