[cagenut]

On the one hand this could be such a cool and powerful concept.

On the other hand my brain segfaults on the recursive loop of how the layer-inversion gets modeled as IaC with a CI/CD pipeline. I guess if you were very strict about having your provider-infra layer (cloudformation/terraform) do only the bare minimum to get your kube environment up, and then within that kube environment you used something like ACK to provision any cloud-provider resources that your kube-managed apps/pipelines needed.

Yet another case where I'm like "I don't know if kube should be the answer to everything, but I sure as shit won't miss <x>".

[rektide]

Yes, the goal is very much to bring provisioning & operations of all resources on to the core platform we're using, Kubernetes. I mentioned in another reply how excited I am to be able to manage things like SQS queues now with my app, via Helm Charts, rather than need separate machinery to manage/operate my app & the various resources it needs.

And now there is a control loop. So if Ben in support accidentally deletes my queue, it'll get recreated.

Breaking away from the proprietary platform underlay is going to be great. Managing things more consistently is going to be really great.