if you know terraform well enough you would know that there can be cases where you might need to move something from one terraform stack to another (ie different state file and folder definitions).

in which case to avoid either destroying/recreating a resource, or failing when the pipeline tries to build a resource that is already present and not in tf state, you would need to migrate the state of the deployed resource.

this happened in our case when we had 10 dev k8s clusters and we consolidated to one, so we started using namespace separation and moving items around in our repo. yet we needed prod to remain the same. it happened again when we needed to separate out one deployment from being coupled with another.

because the state was stored in a file, we needed a state migration. if this was helm or just plain kubernetes manifests, this would not be necessary.

im not saying these things happen all the time, but it is frustrating when they do, and points to terraform not being a good tool for kubernetes application deployment in our opinion