|
49 | 49 |
|
50 | 50 | This will discover deploymentconfigs/deployments/daemonsets/statefulset/rollouts automatically where `foo-configmap` or `foo-secret` is being used either via environment variable or from volume mount. And it will perform rolling upgrade on related pods when `foo-configmap` or `foo-secret`are updated.
|
51 | 51 |
|
52 |
| -You can restrict this discovery to only `ConfigMap` or `Secret` objects that |
| 52 | +You can filter it by the type of monitored resource and use typed versions of `auto` annotation. If you want to discover changes only in mounted `Secret`s and ignore changes in `ConfigMap`s, add `secret.reloader.stakater.com/auto` annotation instead. Analogously, you can use `configmap.reloader.stakater.com/auto` annotation to look for changes in mounted `ConfigMap`, changes in any of mounted `Secret`s will not trigger a rolling upgrade on related pods. |
| 53 | + |
| 54 | +You can also restrict this discovery to only `ConfigMap` or `Secret` objects that |
53 | 55 | are tagged with a special annotation. To take advantage of that, annotate
|
54 | 56 | your deploymentconfigs/deployments/daemonsets/statefulset/rollouts like this:
|
55 | 57 |
|
@@ -84,11 +86,13 @@ will always restart upon a change in configmaps or secrets it uses, regardless
|
84 | 86 | of whether they have the `reloader.stakater.com/match: "true"` annotation or
|
85 | 87 | not.
|
86 | 88 |
|
| 89 | +Similarly, `reloader.stakater.com/auto` and its typed version (`secret.reloader.stakater.com/auto` or `configmap.reloader.stakater.com/auto`) do not work together. If you have both annotations in your deployment, then only one of them needs to be true to trigger the restart. For example, having both `reloader.stakater.com/auto: "true"` and `secret.reloader.stakater.com/auto: "false"` or both `reloader.stakater.com/auto: "false"` and `secret.reloader.stakater.com/auto: "true"` will restart upon a change in a secret it uses. |
| 90 | + |
87 | 91 | 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 `deploymentconfig`, `deployment`, `daemonset`, `statefulset` or `rollout`.
|
88 | 92 | To do this either set the auto annotation to `"false"` (`reloader.stakater.com/auto: "false"`) or remove it altogether, and use annotations for [Configmap](.#Configmap) or [Secret](.#Secret).
|
89 | 93 |
|
90 | 94 | It's also possible to enable auto reloading for all resources, by setting the `--auto-reload-all` flag.
|
91 |
| -In this case, all resources that do not have the auto annotation set to `"false"`, will be reloaded automatically when their ConfigMaps or Secrets are updated. |
| 95 | +In this case, all resources that do not have the auto annotation (or its typed version) set to `"false"`, will be reloaded automatically when their ConfigMaps or Secrets are updated. |
92 | 96 | Notice that setting the auto annotation to an undefined value counts as false as-well.
|
93 | 97 |
|
94 | 98 | ### Configmap
|
@@ -154,6 +158,8 @@ spec:
|
154 | 158 | - `reloader.stakater.com/auto: "true"` will only reload the pod, if the configmap or secret is used (as a volume mount or as an env) in `DeploymentConfigs/Deployment/Daemonsets/Statefulsets`
|
155 | 159 | - `secret.reloader.stakater.com/reload` or `configmap.reloader.stakater.com/reload` annotation will reload the pod upon changes in specified configmap or secret, irrespective of the usage of configmap or secret.
|
156 | 160 | - you may override the auto annotation with the `--auto-annotation` flag
|
| 161 | +- you may override the secret typed auto annotation with the `--secret-auto-annotation` flag |
| 162 | +- you may override the configmap typed auto annotation with the `--configmap-auto-annotation` flag |
157 | 163 | - you may override the search annotation with the `--auto-search-annotation` flag
|
158 | 164 | and the match annotation with the `--search-match-annotation` flag
|
159 | 165 | - you may override the configmap annotation with the `--configmap-annotation` flag
|
|
0 commit comments