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
Copy file name to clipboardExpand all lines: README.md
+98-51
Original file line number
Diff line number
Diff line change
@@ -266,69 +266,116 @@ namespace: reloader
266
266
267
267
Alternatively if you have configured helm on your cluster, you can add Reloader to helm from our public chart repository and deploy it via helm using below-mentioned commands. Follow [this](docs/Helm2-to-Helm3.md) guide, in case you have trouble migrating Reloader from Helm2 to Helm3.
helm install stakater/reloader # For helm3 add --generate-name flag or set the release name
275
-
```
276
277
277
-
**Note:** By default Reloader watches in all namespaces. To watch in single namespace, please run following command. It will install Reloader in `test` namespace which will only watch `Deployments`, `Daemonsets` `Statefulsets` and `Rollouts` in `test` namespace.
278
+
helm install {{RELEASE_NAME}} stakater/reloader -n {{NAMESPACE}} --set reloader.watchGlobally=false # By default, Reloader watches in all namespaces. To watch in single namespace, set watchGlobally=false
278
279
279
-
```bash
280
-
helm install stakater/reloader --set reloader.watchGlobally=false --namespace test # For helm3 add --generate-name flag or set the release name
280
+
helm install stakater/reloader --set reloader.watchGlobally=false --namespace test --generate-name # Install Reloader in `test` namespace which will only watch `Deployments`, `Daemonsets` `Statefulsets` and `Rollouts` in `test` namespace.
281
281
```
282
282
283
-
Reloader can be configured to ignore the resources `secrets` and `configmaps` by using the following parameters of `values.yaml` file:
| resourceLabelSelector | list of comma separated label selectors, if multiple are provided they are combined with the AND operator | string | "" |
303
-
304
-
**Note:** Both `namespaceSelector` & `resourceLabelSelector` can be used together. If they are then both conditions must be met for the configmap or secret to be eligible to trigger reload events. (e.g. If a configMap matches `resourceLabelSelector` but `namespaceSelector` does not match the namespace the configmap is in, it will be ignored).
283
+
#### Uninstalling
305
284
306
-
You can also set the log format of Reloader to JSON by setting `logFormat` to `json` in `values.yaml` and apply the chart.
307
-
308
-
You can enable to scrape Reloader's Prometheus metrics by setting `serviceMonitor.enabled` or `podMonitor.enabled` to `true` in `values.yaml` file. Service monitor will be removed in future releases of Reloader in favour of Pod monitor.
309
-
310
-
**Note:** Reloading of OpenShift (DeploymentConfig) and/or Argo `Rollouts` has to be enabled explicitly because it might not be always possible to use it on a cluster with restricted permissions. This can be done by changing the following parameters:
| isOpenshift | Enable OpenShift DeploymentConfigs. Valid value are either `true` or `false` | boolean | false |
315
-
| isArgoRollouts | Enable Argo `Rollouts`. Valid value are either `true` or `false` | boolean | false |
316
-
| reloadOnCreate | Enable reload on create events. Valid value are either `true` or `false` | boolean | false |
317
-
| syncAfterRestart | Enable sync after Reloader restarts for **Add** events, works only when reloadOnCreate is `true`. Valid value are either `true` or `false` | boolean | false |
318
-
319
-
**isOpenShift** Recent versions of OpenShift (tested on 4.13.3) require the specified user to be in an `uid` range which is dynamically assigned by the namespace. The solution is to unset the runAsUser variable via ``deployment.securityContext.runAsUser=null`` and let OpenShift assign it at install.
320
-
321
-
**reloadOnCreate** controls how Reloader handles secrets being added to the cache for the first time. If reloadOnCreate is set to true:
322
-
323
-
- Configmaps/secrets being added to the cache will cause Reloader to perform a rolling update of the associated workload.
324
-
- When applications are deployed for the first time, Reloader will perform a rolling update of the associated workload.
325
-
- If you are running Reloader in HA mode all workloads will have a rolling update performed when a new leader is elected.
326
-
327
-
If reloadOnCreate is set to false:
328
-
329
-
- Updates to configMaps/Secrets that occur while there is no leader will not be picked up by the new leader until a subsequent update of the configmap/secret occurs. In the worst case the window in which there can be no leader is 15s as this is the LeaseDuration.
285
+
```bash
286
+
helm uninstall {{RELEASE_NAME}} -n {{NAMESPACE}}
287
+
```
330
288
331
-
**Note:** By default, **reloadOnCreate** and **syncAfterRestart** are both set to false. Both need to be enabled explicitly.
|`reloader.isArgoRollouts`| Enable Argo `Rollouts`. Valid value are either `true` or `false`| boolean |`false`|
310
+
|`reloader.isOpenshift`| Enable OpenShift DeploymentConfigs. Valid value are either `true` or `false`| boolean |`false`|
311
+
|`reloader.ignoreSecrets`| To ignore secrets. Valid value are either `true` or `false`. Either `ignoreSecrets` or `ignoreConfigMaps` can be ignored, not both at the same time | boolean |`false`|
312
+
|`reloader.ignoreConfigMaps`| To ignore configMaps. Valid value are either `true` or `false`| boolean |`false`|
313
+
|`reloader.reloadOnCreate`| Enable reload on create events. Valid value are either `true` or `false`| boolean |`false`|
314
+
|`reloader.syncAfterRestart`| Enable sync after Reloader restarts for **Add** events, works only when reloadOnCreate is `true`. Valid value are either `true` or `false`| boolean |`false`|
315
+
|`reloader.reloadStrategy`| Strategy to trigger resource restart, set to either `default`, `env-vars` or `annotations`| enumeration |`default`|
316
+
|`reloader.ignoreNamespaces`| List of comma separated namespaces to ignore, if multiple are provided, they are combined with the AND operator | string |`""`|
317
+
|`reloader.namespaceSelector`| List of comma separated namespaces to select, if multiple are provided, they are combined with the AND operator | string |`""`|
318
+
|`reloader.resourceLabelSelector`| List of comma separated label selectors, if multiple are provided they are combined with the AND operator | string |`""`|
319
+
|`reloader.logFormat`| Set type of log format. Value could be either `json` or `""`| string |`""`|
320
+
|`reloader.watchGlobally`| Allow Reloader to watch in all namespaces (`true`) or just in a single namespace (`false`) | boolean |`true`|
321
+
|`reloader.enableHA`| Enable leadership election allowing you to run multiple replicas | boolean |`false`|
|`reloader.podMonitor.enabled`| Enable to scrape Reloader's Prometheus metrics | boolean |`false`|
358
+
|`reloader.podDisruptionBudget.enabled`| Limit the number of pods of a replicated application | boolean |`false`|
359
+
|`reloader.netpol.enabled`|| boolean |`false`|
360
+
|`reloader.volumeMounts`| Mount volume | array |`[]`|
361
+
|`reloader.volumes`| Add volume to a pod | array |`[]`|
362
+
|`reloader.webhookUrl`| Add webhook to Reloader | string |`""`|
363
+
364
+
#### Additional Remarks
365
+
366
+
- Both `namespaceSelector` & `resourceLabelSelector` can be used together. If they are then both conditions must be met for the configmap or secret to be eligible to trigger reload events. (e.g. If a configMap matches `resourceLabelSelector` but `namespaceSelector` does not match the namespace the configmap is in, it will be ignored).
367
+
- At one time only one of the resources `ignoreConfigMaps` or `ignoreSecrets` can be ignored, trying to do both will cause error in helm template compilation
368
+
- Reloading of OpenShift (DeploymentConfig) and/or Argo `Rollouts` has to be enabled explicitly because it might not be always possible to use it on a cluster with restricted permissions
369
+
-`isOpenShift` Recent versions of OpenShift (tested on 4.13.3) require the specified user to be in an `uid` range which is dynamically assigned by the namespace. The solution is to unset the runAsUser variable via ``deployment.securityContext.runAsUser=null`` and let OpenShift assign it at install
370
+
-`reloadOnCreate` controls how Reloader handles secrets being added to the cache for the first time. If `reloadOnCreate` is set to true:
371
+
1. Configmaps/secrets being added to the cache will cause Reloader to perform a rolling update of the associated workload
372
+
1. When applications are deployed for the first time, Reloader will perform a rolling update of the associated workload
373
+
1. If you are running Reloader in HA mode all workloads will have a rolling update performed when a new leader is elected
374
+
-`serviceMonitor` will be removed in future releases of Reloader in favour of Pod monitor
375
+
- If `reloadOnCreate` is set to false:
376
+
1. Updates to configmaps/secrets that occur while there is no leader will not be picked up by the new leader until a subsequent update of the configmap/secret occurs
377
+
1. In the worst case the window in which there can be no leader is 15s as this is the LeaseDuration
378
+
- By default, `reloadOnCreate` and `syncAfterRestart` are both set to false. Both need to be enabled explicitly
0 commit comments