I don't seem to be able to ignore the annotations placed by Rancher when the resource is declared in a TF module because the

lifecycle

directive isn't legal for a module. Is there another way? The issue is that I have lost the ability to manage with TF by installing Rancher because it has placed annotations out-of-band, thereby creating configuration drift. I am not yet using the Rancher provider in this case, but am exploring using TF and Rancher in the same environment as a prerequisite step. The issue I'm facing applies to Kubernetes resources such as Namespaces.

lifecycle {
        ignore_changes = [
            metadata[0].annotations
        ]
    }