forust
30d2b83efe
Reloader has been running since 23 September and is what makes the reloader.stakater.com/auto annotation on a pod template do anything, but the repository only held a namespace. It was a release someone installed by hand, so it was invisible to review, invisible to Renovate, and one reinstall away from being silently dropped. Declaring it in HELM_RELEASES pins the chart version somewhere Renovate can update it, and the active marker means the namespace is applied before the upgrade instead of only existing as a side effect of the original install. The values file sets nothing the running release does not already do, apart from resource requests and limits, which the chart leaves empty.
21 lines
675 B
YAML
21 lines
675 B
YAML
# Pinned chart: stakater/reloader 2.2.17 (app v1.4.22).
|
|
# Deployed by the deploy workflow, namespace reloader.
|
|
# Restarts pods when a ConfigMap or Secret they consume changes. Opt-in per workload
|
|
# via the reloader.stakater.com/auto: "true" pod annotation; watchGlobally because
|
|
# the workloads that need it are spread across a few dozen namespaces.
|
|
|
|
reloader:
|
|
watchGlobally: true
|
|
|
|
deployment:
|
|
replicas: 1
|
|
# The chart defaults to no requests or limits, so the pod is evictable under node
|
|
# pressure and the restarts go with it.
|
|
resources:
|
|
requests:
|
|
cpu: "10m"
|
|
memory: "64Mi"
|
|
limits:
|
|
cpu: "100m"
|
|
memory: "128Mi"
|