Well, yes, you might be right that the satisfaction of a team drops the longer you use a certain approach. But often, time affects quality. So I would argue that this is more of an organizational issue than a GitOps specific issue. Though, I can see the problems when scaling GitOps to 100+ applications or multiple teams working with this approach.
There is an interesting discussion going on in r/kubernetes about the limitations of gitops. There are good reasons for adopting GitOps, but the linked article points out 6 downsides:
1.Not designed for programmatic updates
2.The proliferation of Git repositories
3.Lack of visibility
4.Doesn’t solve centralised secret management
5.Auditing isn’t as great as it sounds
6.Lack of input validation
Who among you has tried to implement a full GitOps setup? And what was your experience?