Kubernetes on Oxide: How Customer Needs Shaped Our Integrations

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-oxide` on my bingo card...

	▲	thegagne 3 minutes ago \| parent [-]
		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 complexity and also shortcomings of products on the market for this stuff, both in the cloud and on prem.

▲

overflowy 34 minutes ago | parent | prev | next [-]

I would absolutely kill for them to open source their documentation system.

▲

bcantrill 22 minutes ago | parent [-]

Are you referring to our RFD system?[0][1] Because if so, good news![2]

[0] https://rfd.shared.oxide.computer/rfd/0001

[1] https://oxide-and-friends.transistor.fm/episodes/rfds-the-ba...

[2] https://github.com/oxidecomputer/rfd-site

	▲	overflowy 19 minutes ago \| parent [-]
		OMG, you just made my day!

▲

pianoben 26 minutes ago | parent | prev [-]

I have seldom wanted anything as much as I want an Oxide rack at home. Maybe in 40 years we'll start to see the first ones show up in surplus auctions...