Reloader By R-1n Github -

The Helm chart is maintained alongside the main project:

helm repo add reloader https://r-1n.github.io/reloader
helm repo update
helm install reloader reloader/reloader --namespace reloader --create-namespace

Helm allows easy overrides, such as setting log level, watch namespace, or enabling auto-reload for all resources.

For high availability across nodes, you can deploy Reloader as a DaemonSet instead of a Deployment (not recommended for most clusters). reloader by r-1n github

Reloader uses a straightforward annotation strategy to determine which resources to update.

1. Auto-Discovery (The Easy Way) Simply add an annotation to your Deployment. Reloader will automatically track all ConfigMaps and Secrets referenced by that Deployment. The Helm chart is maintained alongside the main

kind: Deployment
metadata:
  annotations:
    secret.reloader.stakater.com/reload: "true"

2. Specific Resource Targeting If you only want to restart a deployment when a specific Secret changes (ignoring others), you can specify the name:

kind: Deployment
metadata:
  annotations:
    secret.reloader.stakater.com/reload: "my-secret-name"

apiVersion: v1
kind: ConfigMap
metadata:
  name: app-config
data:
  app.properties: |
    color=blue
    timeout=30s

Use the watch-* annotations to narrow which resources trigger a reload. Alternatively, set reload-on-change: "false" on stable workloads. Helm allows easy overrides, such as setting log

GitHub Repository: r-1n/reloader (Note: If this URL is incorrect, please verify the exact repository name)