One example is PodDisruptionBudget, another is RBAC objects (role binding cannot be changed to reference a different role IIRC).
For immutable resource kinds we should either implement a custom code, or just add some way of adding "immutable" flag per kind which will tell Smith to delete-and-create instead of updating if the spec is different.
One example is
PodDisruptionBudget, another is RBAC objects (role binding cannot be changed to reference a different role IIRC).For immutable resource kinds we should either implement a custom code, or just add some way of adding "immutable" flag per kind which will tell Smith to delete-and-create instead of updating if the spec is different.