Ignoring changes in-cluster changes to annotation & label

[lucapericlp]

Not sure if this will be helpful, I haven't looked into this deeply but I'm assuming that after the first terraform apply, annotations & labels are getting updated for the flyte-tls-secret (by cert-manager?). I've had to add this in order to make any future changes without disrupting current state.

[lucapericlp]

@davidmirror-ops can't assign you as a reviewer so just light ping. This repo was super useful in setting things up, kudos!

[davidmirror-ops]

@lucapericlp thanks for the nice comments and the PR!

I'm assuming that after the first terraform apply, annotations & labels are getting updated for the flyte-tls-secret (by cert-manager?).

Good question. I don't have a GKE environment handy but could you share the output of kubectl describe secret flyte-tls-secret -n flyte? I'm not familiar with a use case that would change secret's labels or annotations after deployment