-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
HCM has a zillion [Selector]SyncSets. When we get support requests, the root cause is often that different [S]SSes are hitting the same objects, overwriting each other. (The last one "wins".) This instance was prompted by #itn-2024-00216.
This card is to investigate/implement emitting some kind of warning when one ClusterSync (which represents the sum total of all [S]SSes applied to one cluster) is hitting the same object more than once.
Consideration: It is a possible reasonable use case that a resources (or even secretMappings?) entry subsequently gets patches applied to it. Do we warn in this case? But multiple resources hitting the same kvg/ns/name should definitely be a warning!
Consideration: Where do we put the warning? Maybe a status field for conflicts? And a printColumn for regular (maybe a WARNINGS column with a count as the value?) and wide (enumerates the warnings).