Currently secrets created in the cluster are setup with annotations showing they were generated via mimir. However, there are no timestamps or versions attached, so it can be unclear as to exacly where the secret was sourced from ala versions or time.
This issue will look into implementing a versioning approach that provides the secret version to the cluster. This way pods/sidecars reading the secrets have an easy way of detecting when mimir has propagated a change to the secret, and can handle that according to their own requirements.
Currently secrets created in the cluster are setup with annotations showing they were generated via mimir. However, there are no timestamps or versions attached, so it can be unclear as to exacly where the secret was sourced from ala versions or time.
This issue will look into implementing a versioning approach that provides the secret version to the cluster. This way pods/sidecars reading the secrets have an easy way of detecting when mimir has propagated a change to the secret, and can handle that according to their own requirements.