github/Reloader
1
0
Fork 0
mirror of https://github.com/stakater/Reloader.git synced 2026-09-03 14:47:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adds note on incompatibility with 'reloader.stakater.com/auto'.

Browse Source
This commit is contained in:
Vlad Losev
2020-06-21 14:15:58 -07:00
parent 6bcec06052
commit e61f9a6bdb
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -3
View File
@@ -51,8 +51,8 @@ spec:
template:
```
and Reloader will trigger the rolling upgrade when any `ConfigMap` or `Secret` annotated like this:
and then annotate your `ConfigMap` or `Secret` so:
and Reloader will trigger the rolling upgrade upon modification of any
`ConfigMap` or `Secret` annotated like this:
```yaml
kind: ConfigMap
@@ -63,7 +63,15 @@ data:
key: value
```
is modified, provided it is being used in an environment variable or a volume mount.
provided the secret/configmap is being used in an environment variable or a
volume mount.
Please note that `reloader.stakater.com/search` and
`reloader.stakater.com/auto` do not work together. If you have the
`reloader.stakater.com/auto: "true"` annotation on your deployment, then it
will always restart upon a change in configmaps or secrets it uses, regardless
of whether they have the `reloader.stakater.com/match: "true"` annotation or
not.
We can also specify a specific configmap or secret which would trigger rolling upgrade only upon change in our specified configmap or secret, this way, it will not trigger rolling upgrade upon changes in all configmaps or secrets used in a deployment, daemonset or statefulset.
To do this either set the auto annotation to `"false"` (`reloader.stakater.com/auto: "false"`) or remove it altogether, and use annotations mentioned [here](#Configmap) or [here](#Secret)