Source Hydrated Infrastructure Models
medium.comThis sound cool and all, but how would this concept work for traditional VMS and physical servers, running OSes like Windows or some baremetal hypervisor? All I see is kubernetes, kubernetes, kubernetes... but real-world infrastructure also consists of VMs too and yes even physical servers, and in most enterprises, that also means running Windows.
The infrastructure layer would have to create the interface for a custom operator to reconcile with. There are a fair bit of bridges out there to enable this. There's now Kubevirt for VM management and Metal3 for baremetal configurations as well. If the operator isn't readily available from the selection of community solutions, the platform team would have to implement it themselves. Kubernetes is really just a glorified etcd store for any manifest schema (CRD) you implement alongside a reconciling controller. It just so happens that the default use case of it was designed for container orchestration. Once you look past Kubernetes as purely a container orchestration tool, you can use its paradigm to implement your own declarative reconciliation logic for anything.
I know that's not a satisfactory answer but the infrastructure models (for VMs or Windows machines) would have to be implemented into the new paradigm bit by bit to make this work. This used to be something that was laborious but you could have Claude Code cook up something for the loop interfaces and have a working controller prototype in a short time.
Not saying the integration is going to be simple though. The team has to actually buy in and prioritise building the controller logic for each platform solution. And that includes reviewing the code slop that Claude creates.