please expand on this, I am interested (for real!)

Rug pulls on infrastructure components seem even worse than other rug pulls as they can hit your entire infra codebase at once

This is why infrastructure people are conservative by nature, it's so damn much gruntwork to migrate without downtime

And it happens while we are all very enthusiastically dedicated to migrating off Kubernetes ingress-nginx. Just as planned.

As an Infrastructure Engineer who used it: I blame people who didnt help fund/maintain it (including ourselves)

Probably Pulumi

I'll be honest Pulumi is pretty cool but I'm a little worried by how high on the stack it is. I wonder if the same thing won't happen to them that's happening to CDKTF here.

Terraform is ugly but it works well enough for me and seems ingrained enough to be durable to this kind of thing (i.e. I bet for sure the community would pick it up (I wish I could say that I'm part of that community but I can't say I use it quite that often))

> I wonder if the same thing won't happen to them that's happening to CDKTF here.

This is clearly a business decision rather than technical.

Pulumi is meant to be semi-automated (in generating the bridges) so perhaps is slightly better off in maintenance.

It could finally solve the major pain in using Node over Docker for CI and local development.

https://medium.com/@mfornasa/using-yarn-with-docker-c116ad28...

@k__: you're right, but the article does not consider the long-term downtime, which is a bit harder to measure (and it does affect the user-experience less than a 5% loss rate). The solution for long-term downtime is having a backup connection on a different medium and with a different service provider.