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
By default, Reloader gets deployed in `default` namespace and watches changes `secrets` and `configmaps` in all namespaces.
193
+
By default, Reloader gets deployed in `default` namespace and watches changes `secrets` and `configmaps` in all namespaces.Additionally, in the default Reloader deployment, the following resource limits and requests are set:
194
+
195
+
```yaml
196
+
resources:
197
+
limits:
198
+
cpu: 150m
199
+
memory: 512Mi
200
+
requests:
201
+
cpu: 10m
202
+
memory: 128Mi
203
+
```
194
204
195
205
Reloader can be configured to ignore the resources `secrets` and `configmaps` by passing the following arguments (`spec.template.spec.containers.args`) to its container :
|`reloader.matchLabels`| Pod labels to match | map |`{}`|
342
+
|`reloader.enableMetricsByNamespace`| Expose an additional Prometheus counter of reloads by namespace (this metric may have high cardinality in clusters with many namespaces) | boolean |`false`|
Reloader can also export a metric to show the number of reloads by namespace. This feature is disabled by default, as it can lead to high cardinality in clusters with many namespaces.
67
+
68
+
The metric will have both `success` and `namespace` as attributes:
0 commit comments