Description
Is your feature request related to a problem? Please describe..
In complex deployment, it has happened sometimes that two AKVS entries were generated, defining the same secret. This results in the secret being repeatedly deleted and re-created, which can cause instability in the cluster, especially if a reloader solution restarts workload if it detects that configuration has changed.
Describe the solution you'd like
It would be nice if akv2k8s could raise an error if two AKVS are defined generating the same secret.
Describe alternatives you've considered
We have this sanity check as part of certain deployment solutions we have, but such solution doesn't integrate well with everything and covers only a subset of the cases where things can go wrong.
Thank you very much!