4 ms·
So yet another example of people piggybacking on the Kubernetes manifests & inner loop to define and apply resources on other APIs. I wonder when some places wi
by darkwater 3y ago
So yet another example of people piggybacking on the Kubernetes manifests & inner loop to define and apply resources on other APIs.
I wonder when some places will start to provision dedicated k8s masters just to run their IaC loop, instead of running actual workload...
- dboreham 3y agoCould call that project "tortuga".
- spdustin 3y agoTortugas hasta el final, in fact.
- kodama-lens 3y agoYou mean everyone that runs a Crossplane cluster? Already happening
- MrDarcy 3y agoAlready happening. A control plane only cluster is an excellent replacement for Hashicorp Vault for example. See also the Cluster API to manage other clusters and Crossplane to manage anything Terraform would have managed.
- darkwater 3y ago> Already happening. A control plane only cluster is an excellent replacement for Hashicorp Vault for example. Vault? Don't you mean Terraform (Enterprise), or platforms based on TF that do that kind of thing (converging platform to its code definition, automatically). I don't really understand why (and how) one would use K8s API server as a replacement for HC Vault.
- nijave 3y agoIt has RBAC, service accounts, and Secrets all with APIs. I guess you could automate provisioning storage accounts on nodes or have a system that creates tokens with the cluster key. Not sure that's really any better than not using it, though
- dilyevsky 3y agoWe do that - chucked all kubernetes apis and run an apiserver with our own apis + controllers to reconcile state. It’s a bit of work to make it work bc the tooling is obviously not designed for this but you can make it happen