Reloader is a Kubernetes tool that automatically reloads configuration files in a running container when a change is detected. This can be useful for updating configurations without having to manually restart your application. This blog will walk through the process of setting up Reloader in Kubernetes. It will provide an example of MySQL deployment to enable reloader using annotations and MySQL deployment YAML to watch for changes in secrets.
Create deployment YML for MySQL container using above Secrets, PVC and PV:
kubectl apply -f my-sql.yaml
apiVersion: v1
kind: Service
metadata:
name: mysql
spec:
ports:
- port: 3306
selector:
app: mysql
clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mysql
annotations:
reloader.stakater.com/auto: "true"
spec:
selector:
matchLabels:
app: mysql
replicas: 3
strategy:
type: Recreate
template:
metadata:
labels:
app: mysql
spec:
containers:
- image: mysql:5.6
name: mysql
env:
# Use secret in real usage
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: demo-secret
key: password
ports:
- containerPort: 3306
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: mysql-pv-claim
Once deployed, you can verify the pods status:
Kubectl get pods
kubectl get pods
NAME READY STATUS RESTARTS AGE
mysql-5b8d8bd99b-277mf 1/1 Running 0 10s
mysql-5b8d8bd99b-6x5wz 1/1 Running 0 10s
mysql-5b8d8bd99b-srlnb 1/1 Running 0 10s
Describing the pod to view details:
kubectl describe deployment mysql
Name: mysql
Namespace: keyva
CreationTimestamp: Sun, 19 Feb 2023 20:28:02 -0600
Labels: <none>
Annotations: deployment.kubernetes.io/revision: 1
reloader.stakater.com/auto: true
Selector: app=mysql
Replicas: 3 desired | 3 updated | 3 total | 3 available | 0 unavailable
StrategyType: Recreate
MinReadySeconds: 0
Pod Template:
Labels: app=mysql
Containers:
mysql:
Image: mysql:5.6
Port: 3306/TCP
Host Port: 0/TCP
Environment:
MYSQL_ROOT_PASSWORD: <set to the key 'password' in secret 'demo-secret'> Optional: false
Mounts:
/var/lib/mysql from mysql-persistent-storage (rw)
Volumes:
mysql-persistent-storage:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: mysql-pv-claim
ReadOnly: false
Conditions:
Type Status Reason
---- ------ ------
Progressing True NewReplicaSetAvailable
Available True MinimumReplicasAvailable
OldReplicaSets: <none>
NewReplicaSet: mysql-5b8d8bd99b (3/3 replicas created)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set mysql-5b8d8bd99b to 3
Next, validate the Reloader by changing the secret values and redeploy the secret.yaml file. You should see the MySQL pods restart to pick reference the new secret value.
Reloader can monitor changes to ConfigMap and Secret, as well as perform rolling upgrades on Pods and their associated DeploymentConfigs, Deployments, Daemonsets Statefulsets, and Rollouts.
Validation of reloader:
kubectl logs reloader-reloader-7f6b8d49f7-9lxrx
time="2023-02-22T01:59:48Z" level=info msg="Changes detected in 'demo-secret' of type 'SECRET' in namespace 'keyva', Updated 'mysql' of type 'Deployment' in namespace 'keyva'"
Verify the age of Pods:
kubectl get pods
NAME READY STATUS RESTARTS AGE
mysql-7bd6b6d789-fqfgd 1/1 Running 0 3s
mysql-7bd6b6d789-tbxxp 1/1 Running 0 3s
mysql-7bd6b6d789-trd7v 1/1 Running 0 3s
[post_title] => Reloader - K8 - Rapid - Rollouts
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => reloader-k8-rapid-rollouts
[to_ping] =>
[pinged] =>
[post_modified] => 2023-04-21 17:06:07
[post_modified_gmt] => 2023-04-21 17:06:07
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://keyvatech.com/?p=3743
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
) [1] => WP_Post Object
(
[ID] => 3709
[post_author] => 7
[post_date] => 2023-02-10 18:43:05
[post_date_gmt] => 2023-02-10 18:43:05
[post_content] => Keyva is pleased to announce the certification of the Keyva Integration for Red Hat Ansible AutomationPlatform for the new ServiceNow Utah release. Clients can now seamlessly upgrade their ServiceNow App from previous ServiceNow releases (Tokyo, Rome, San Diego) to the Utah release. The Utah release includes various updates to products, applications, and features for Customer Experience, Technology Excellence, Automation & Low-Code, Now Platform, and Industries. Learn more about the Keyva ServiceNow Integrations Red Hat products and view all the ServiceNow releases for which Keyva has been certified at the ServiceNow store, visit bit.ly/3lsquOb.
[post_title] => Keyva ServiceNow App for Red Hat Ansible Automation Platform – Certified for Utah Release
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => keyva-servicenow-app-for-red-hat-ansible-automation-platform-certified-for-utah-release
[to_ping] =>
[pinged] =>
[post_modified] => 2024-05-28 18:29:51
[post_modified_gmt] => 2024-05-28 18:29:51
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://keyvatech.com/?p=3709
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
) [2] => WP_Post Object
(
[ID] => 3685
[post_author] => 7
[post_date] => 2022-12-06 16:08:45
[post_date_gmt] => 2022-12-06 16:08:45
[post_content] =>
Keyva is pleased to announce the certification of our ServiceNow App for Red Hat Ansible for the new ServiceNow Tokyo release. Clients can now seamlessly upgrade their ServiceNow App from previous ServiceNow releases (Rome, San Diego) to the Tokyo release.
According to ServiceNow, the Tokyo release is purpose‑built to deliver better employee and customer experiences, supercharge automation and trust in operations, and accelerate value in ways that are good for people, good for the planet, and good for profits. Tokyo release is the latest version since the company’s inception.
Learn more about the Keyva ServiceNow App for Ansible and view all the ServiceNow releases for which it has been certified at the ServiceNow store, visit bit.ly/3VTl0ZM.
Keyva CEO Jaime Gmach discusses how we help clients move data, applications, and other workflows from on-premise to the cloud. [post_title] => Keyva: Cloud Migration
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => keyva-cloud-migration
[to_ping] =>
[pinged] =>
[post_modified] => 2023-06-28 17:55:14
[post_modified_gmt] => 2023-06-28 17:55:14
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://keyvatech.com/?p=3422
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
) [4] => WP_Post Object
(
[ID] => 3684
[post_author] => 2
[post_date] => 2022-11-02 16:42:23
[post_date_gmt] => 2022-11-02 16:42:23
[post_content] =>
https://youtu.be/9zr1gzEEYCs
Keyva CEO Jaime Gmach discusses how Keyva helps build and maintain integrations between the tools and solutions our clients frequently use in a way that is secure, scalable, and supportable.
Reloader is a Kubernetes tool that automatically reloads configuration files in a running container when a change is detected. This can be useful for updating configurations without having to manually restart your application. This blog will walk through the process of setting up Reloader in Kubernetes. It will provide an example of MySQL deployment to enable reloader using annotations and MySQL deployment YAML to watch for changes in secrets.
Create deployment YML for MySQL container using above Secrets, PVC and PV:
kubectl apply -f my-sql.yaml
apiVersion: v1
kind: Service
metadata:
name: mysql
spec:
ports:
- port: 3306
selector:
app: mysql
clusterIP: None
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: mysql
annotations:
reloader.stakater.com/auto: "true"
spec:
selector:
matchLabels:
app: mysql
replicas: 3
strategy:
type: Recreate
template:
metadata:
labels:
app: mysql
spec:
containers:
- image: mysql:5.6
name: mysql
env:
# Use secret in real usage
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: demo-secret
key: password
ports:
- containerPort: 3306
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: mysql-pv-claim
Once deployed, you can verify the pods status:
Kubectl get pods
kubectl get pods
NAME READY STATUS RESTARTS AGE
mysql-5b8d8bd99b-277mf 1/1 Running 0 10s
mysql-5b8d8bd99b-6x5wz 1/1 Running 0 10s
mysql-5b8d8bd99b-srlnb 1/1 Running 0 10s
Describing the pod to view details:
kubectl describe deployment mysql
Name: mysql
Namespace: keyva
CreationTimestamp: Sun, 19 Feb 2023 20:28:02 -0600
Labels: <none>
Annotations: deployment.kubernetes.io/revision: 1
reloader.stakater.com/auto: true
Selector: app=mysql
Replicas: 3 desired | 3 updated | 3 total | 3 available | 0 unavailable
StrategyType: Recreate
MinReadySeconds: 0
Pod Template:
Labels: app=mysql
Containers:
mysql:
Image: mysql:5.6
Port: 3306/TCP
Host Port: 0/TCP
Environment:
MYSQL_ROOT_PASSWORD: <set to the key 'password' in secret 'demo-secret'> Optional: false
Mounts:
/var/lib/mysql from mysql-persistent-storage (rw)
Volumes:
mysql-persistent-storage:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: mysql-pv-claim
ReadOnly: false
Conditions:
Type Status Reason
---- ------ ------
Progressing True NewReplicaSetAvailable
Available True MinimumReplicasAvailable
OldReplicaSets: <none>
NewReplicaSet: mysql-5b8d8bd99b (3/3 replicas created)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set mysql-5b8d8bd99b to 3
Next, validate the Reloader by changing the secret values and redeploy the secret.yaml file. You should see the MySQL pods restart to pick reference the new secret value.
Reloader can monitor changes to ConfigMap and Secret, as well as perform rolling upgrades on Pods and their associated DeploymentConfigs, Deployments, Daemonsets Statefulsets, and Rollouts.
Validation of reloader:
kubectl logs reloader-reloader-7f6b8d49f7-9lxrx
time="2023-02-22T01:59:48Z" level=info msg="Changes detected in 'demo-secret' of type 'SECRET' in namespace 'keyva', Updated 'mysql' of type 'Deployment' in namespace 'keyva'"
Verify the age of Pods:
kubectl get pods
NAME READY STATUS RESTARTS AGE
mysql-7bd6b6d789-fqfgd 1/1 Running 0 3s
mysql-7bd6b6d789-tbxxp 1/1 Running 0 3s
mysql-7bd6b6d789-trd7v 1/1 Running 0 3s
By: Saikrishna Madupu – Sr Devops Engineer Reloader is a Kubernetes tool that automatically reloads configuration files in a running container when a change is detected. This can be useful for updating ...
Keyva is pleased to announce the certification of the Keyva Integration for Red Hat Ansible Automation Platform for the new ServiceNow Utah release. Clients can now seamlessly upgrade their ServiceNow ...
Keyva is pleased to announce the certification of our ServiceNow App for Red Hat Ansible for the new ServiceNow Tokyo release. Clients can now seamlessly upgrade their ServiceNow App from ...
Keyva CEO Jaime Gmach discusses how Keyva helps build and maintain integrations between the tools and solutions our clients frequently use in a way that is secure, scalable, and supportable.
Keyva CEO Jaime Gmach shares how end-to-end automation is at the core of how we help clients drive business value and technical capabilities from their IT environment.
