going to give an architecture preview of the karpenter cluster-api provider proof-of-concept tomorrow at the cluster api office hours. in preparation for that i am sharing the code i have been hacking on so far.
it's nowhere near ready for use as i am still implementing the provider interfaces, but in the spirit of open i feel better having this in the public.
@alexhammy it's not functional yet, but i am working towards establishing an architecture with the community.
@alexhammy apologies, i misunderstood, by "tf" do you mean tensorflow?
@elmiko I meant Terraform/OpenToFu but I see it's an operator? I think?
@alexhammy ahh, yeah, it's an operator that will utilize the karpenter core library to manage scaling in the cluster.
see https://karpenter.sh for a better explanation of the core project.
the underlying bits use cluster-api for infrastructure provisioning, which has several different provider implementations, none using tf/ot.
@alexhammy here's the core cluster-api stuff, https://cluster-api.sigs.k8s.io
@elmiko right I'm pretty familiar with Karpenter, I had no idea about this cluster-api (why don't they call that provider api to be less confusing) - anyway that's super cool!
@alexhammy i'm not sure about the history of the name, it was established before i started contributing there. it was born from sig cluster lifecycle though, so maybe that was part of the inspiration.
@jack there are AWS and Azure varriants currently, and i've heard a GCP version is being implemented.