What is the purpose of kubenix/hash?

[felixscheinost]

I wonder what the benefit of the kubenix/hash label is?

We use kubenix in combination with ArgoCD and for big apps a small change causes that label to change everywhere.
That again makes it hard to find the real change in the ArgoCD diff.

What would be cases where the kubenix/hash is required?
Would it make sense to make it opt-out?

[adrian-gierakowski]

Imho it’s useless and as you noted creates noise. I believe motivation could have been to trigger a rollout of deployments etc whenever anything changes in the manifest group. But for that what you really need is hashed configmap\secret names.

I’ve been using manifest without hash on my fork (mind you it’s a fork of the original kubenix not the one from this repo). I’ve also got code to automatically hash config map names (like kustomize does). I think that one is in private repo but I wouldn’t mind sharing).

[felixscheinost]

Do you think an opt-out like that (#76) would make sense?

[adrian-gierakowski]

Yes, an option to toggle it is better than what I’ve done on my fork.