stevehipwell

I'd assumed @sudomateo was talking about you when he said his colleague had built a prototype.

My point was that the major cloud CCMs are rooted (at least spiritually) in in-tree implementations. With Oxide having an API first strategy (similar in principle to a major cloud provider) the direction you take on your greenfield CCM could be interesting.

RE Karpenter, it always seemed like a natural fit for Oxide, even more so than some of the currently implementors. And now you have the expertise in the team, I'd be really interested in the reason if you don't go down that path.

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...

AFAIK the official Crossplane providers for AWS, GCP & Azure are built on the respective Hashicorp owned Terraform providers; so I'm not sure how this is going to impact them?