Reloader

To enable Reloader to automatically watch and trigger rollouts for a workload, add the reloader.stakater.com/auto: "true" annotation to the workload's metadata. Reloader will then monitor any ConfigMap or Secret referenced within the workload's specification (e.g., via envFrom or volumeMounts) and trigger a rollout when they change.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app
  annotations:
    reloader.stakater.com/auto: "true"
spec:
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
        - name: app
          image: your-image
          envFrom:
            - configMapRef:
                name: my-config
            - secretRef:
                name: my-secret

You can install Reloader using raw Kubernetes manifests or Kustomize.

Vanilla Manifests:

kubectl apply -f https://raw.githubusercontent.com/stakater/Reloader/master/deployments/kubernetes/reloader.yaml

Vanilla Kustomize:

kubectl apply -k https://github.com/stakater/Reloader/deployments/kubernetes

Reloader can send alerts to a webhook endpoint (Slack, Microsoft Teams, Google Chat, or generic webhooks) whenever a rolling upgrade is triggered. Enable this in your Helm values.yaml under reloader.deployment.env.secret.

reloader:
  deployment:
    env:
      secret:
        ALERT_ON_RELOAD: "true"
        ALERT_SINK: "slack"
        ALERT_WEBHOOK_URL: "<your-webhook-url>"
        ALERT_ADDITIONAL_INFO: "Triggered by Reloader in staging environment"

For fine-grained control, use the 'Search' pattern. A workload will only restart if the Secret/ConfigMap is both referenced by the workload and explicitly marked as eligible for reload.

1. On the Workload: Add reloader.stakater.com/search: "true".
2. On the ConfigMap/Secret: Add reloader.stakater.com/match: "true".
3. Requirement: The resource must be referenced in the workload (via env, volumeMount, etc.).

# On the Workload
metadata:
  annotations:
    reloader.stakater.com/search: "true"
---
# On the ConfigMap or Secret
metadata:
  annotations:
    reloader.stakater.com/match: "true"

To be listed in the Reloader ADOPTERS.md file with a logo in the visual grid, follow these steps:

1. Fork the repository.
2. Add your company logo to the /adopters/logos/ directory.
   • Use SVG (preferred) or PNG.
   • Name the file after your company (e.g., acme-corp.svg).
   • Ensure the file size is under 100KB.
3. Add a new row to the Adopter Details table in ADOPTERS.md.
4. Open a Pull Request with the commit title format: docs: add <YOUR COMPANY> to ADOPTERS.md.

To remove Reloader from your cluster, use the Helm uninstall command specifying the release name and the namespace where it was installed.

helm uninstall {{RELEASE_NAME}} -n {{NAMESPACE}}

When installing via Helm, you can prevent Reloader from monitoring Jobs and CronJobs by setting the corresponding flags to true.

helm install stakater/reloader --set reloader.ignoreJobs=true --set reloader.ignoreCronJobs=true --generate-name

If you do not want to use Git, you can request to be added by posting a comment in the 👋 Show & Tell: Who's using Reloader? GitHub discussion. Use the following template:

**Company / Team:**
**Quote:** (1–2 lines on how Reloader helps you)
**Use case:** (e.g. secret rotation, cert-manager, GitOps pipeline)
**Scale:** (clusters, namespaces, workloads — share what you're comfortable with)
**Since:** (approximate year)
**Logo:** (attach an SVG or PNG if you'd like to appear in the grid)

The maintainers will handle the Pull Request on your behalf.