You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few places in the helm chart annotate Deployments (and other pod-template-y things) with hashed references to secrets. This practice appears to be intended to cause pods to roll when the referenced secret changes.
We aim to keep the following list of examples up-to-date as we discover them while building parity between the helm chart and the appliance:
In some of these examples, changes to the underlying referenced secrets' content do not appear to cause pods to roll, since it's just hashing the names. We could consider using a mechanism such as https://github.com/stakater/Reloader in the appliance, to ensure that pods do roll.
The text was updated successfully, but these errors were encountered:
There are a few places in the helm chart annotate Deployments (and other pod-template-y things) with hashed references to secrets. This practice appears to be intended to cause pods to roll when the referenced secret changes.
We aim to keep the following list of examples up-to-date as we discover them while building parity between the helm chart and the appliance:
checksum/redis
annotationchecksum/pgsql.secret
annotationIn some of these examples, changes to the underlying referenced secrets' content do not appear to cause pods to roll, since it's just hashing the names. We could consider using a mechanism such as https://github.com/stakater/Reloader in the appliance, to ensure that pods do roll.
The text was updated successfully, but these errors were encountered: