apiVersion: v1
kind: ConfigMap
metadata:
name: nginx-config
data:
site.conf: |
server
listen 80;
server_name example.com;
location / proxy_pass http://backend;
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
annotations:
reloader.r1n.com/configmap: "nginx-config"
spec:
replicas: 3
template:
spec:
containers:
- name: nginx
image: nginx
volumeMounts:
- name: conf
mountPath: /etc/nginx/conf.d
volumes:
- name: conf
configMap:
name: nginx-config
Edit site.conf to change server_name → Reloader triggers a rolling update. Zero config staleness.
To reload only when specific resources change:
annotations:
configmap.reloader.stakater.com/reload: "app-config,cache-config"
secret.reloader.stakater.com/reload: "db-credentials"
With the above, only changes to app-config, cache-config, or db-credentials trigger a restart. reloader by r1n github
Hosted on GitHub, r1n’s Reloader is a lightweight, zero-dependency command-line tool designed to watch your file system and automatically rebuild and restart your Go application when changes are detected.
In the crowded space of "hot reload" tools for Go, Reloader stands out for its simplicity and specific design philosophy. It doesn't try to be a massive task runner or a complex process manager. It does one thing and does it well: It watches your files and restarts your app. Edit site
If you are a developer, you know the drill. You write code, save the file, switch to your terminal, stop the running process, and restart it manually to see the changes. It’s a loop that happens dozens of times a day, interrupting your flow and eating up precious minutes.
Wouldn't it be better if your application restarted automatically every time you saved a file? With the above, only changes to app-config ,
Enter Reloader by r1n, a lightweight, open-source utility available on GitHub designed to solve exactly this problem. In this post, we’ll explore what Reloader is, how to install it, and why it deserves a spot in your development toolkit.