Secrets are piled up while applying same serviceaccount

[harshajith]

I was applying a ServiceAccount resource using KubeResourceHandler which in turn uses NamespaceVisitFromServerGetWatchDeleteRecreateWaitApplicableImpl. However, while comparing objects even though it is the same serviceaccount, object comparison fails due to the secrets attached in the previously created ServiceAccount. Hence, it tries to replace the same ServiceAccount adding new secrets.

If you keep applying the same resource, it will consequently add up secrets.
Seems it needs to reuse the same secrets instead of adding new secrets. #