Exactly. The problem isn't that you're using the cloud. It's that you're kidding yourself by calling the YAML "Kubernetes". That file is a cloud vendor config with a k8s API veneer.
I've spent weeks stripping those annotations out of a "lift and shift" that was supposed to be easy. The real work wasn't the pods, it was untangling the fifty lines of vendor logic hidden behind `alb.ingress.kubernetes.io`. That's where you live now.
If it ain't broke, don't 'upgrade' it.
That "k8s API veneer" is a good way to put it. It makes the config feel like a standard, which can be misleading.
If the real work is untangling annotations, when does it make sense to just accept them as part of your stack? Is there a threshold where you'd decide the abstraction isn't worth the effort?