Geeting Issue While Using Reloader In ConfigMap about reloader

[kahootali]

Is Reloader running globally? If not, make sure the deployments are running in same namespace as that of reloader. And secondly, make sure both the deployments have the reloader annotation.

[loknathsingh]

@kahootali Thank you and your team.
It working fine as per our Requirment.

[kahootali]

@loknathsingh can you please share the k8s version and reloader version, you are using? And can you kindly format the Deployment and Configmap template above.

[loknathsingh]

k8s version :v1.11.3

[loknathsingh]

apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
labels:
app: nginx
annotations:
configmap.reloader.stakater.com/reload: "nginx-configmap"
spec:
selector:
matchLabels:
app: nginx
replicas: 3
template:
metadata:
labels:
app: nginx
spec:
containers:

• name: nginx
  image: nginx
  ports:
• containerPort: 80
  volumeMounts:
• name: nginx-config1
  mountPath: /etc/nginx/conf.d/default.conf
  subPath: default.conf
  volumes:
• name: nginx-config1
  configMap:
  name: nginx-configmap

[kahootali]

@loknathsingh I have tested it with following config, it is working fine.

apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
  annotations:
    configmap.reloader.stakater.com/reload: "nginx-configmap"
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 2 # tells deployment to run 2 pods matching the template
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
  annotations:
    configmap.reloader.stakater.com/reload: "nginx-configmap"
  spec:
    selector:
      matchLabels:
      app: nginx
    replicas: 3
    template:
      metadata:
        labels:
          app: nginx
        spec:
          containers:
            name: nginx
            image: nginx
            ports:
              containerPort: 80
            volumeMounts:
              name: nginx-config1
              mountPath: /etc/nginx/conf.d/default.conf
              subPath: default.conf
    volumes:
      name: nginx-config1
      configMap:
        name: nginx-configmap
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: nginx-configmap
  namespace: default
data:
  default.conf: |
    upstream backend {
      server 172.27.15.8:8081;
      server 192.0.0.1 backup;
      }
    server {
        location / {
            proxy_pass http://backend;
        }
    }

[kahootali]

@loknathsingh kindly try again and let us know, I am closing the issue for now, feel free to open again if you face any issue

[loknathsingh]

@kahootali our requirement is to Restart pods when we make any changes in configmap using reloader.
and we are getting this but in only one deployment. not in other...
I am sharing logs of that.............
time="2019-01-24T08:26:13Z" level=info msg="Changes detected in nginx-configmap of type 'CONFIGMAP' in namespace: default"
time="2019-01-24T08:26:14Z" level=info msg="Updated nginx-deployment of type Deployment in namespace: default "
time="2019-01-24T08:38:40Z" level=info msg="Changes detected in filebeat-config-map of type 'CONFIGMAP' in namespace: default"
time="2019-01-24T08:38:40Z" level=info msg="Updated ddddm-filebeat of type Deployment in namespace: default "
time="2019-01-24T08:43:36Z" level=info msg="Changes detected in filebeat-config-map of type 'CONFIGMAP' in namespace: default"
time="2019-01-24T08:43:36Z" level=info msg="Updated ddm-filebeat of type Deployment in namespace: default "
time="2019-01-24T09:31:44Z" level=info msg="Changes detected in serviceconfig-config-map of type 'CONFIGMAP' in namespace: default

[kahootali]

What do you mean by

we are getting this but in only one deployment. not in other...

In logs above, it shows that it has updated nginx-deployment as well as ddddm-filebeat.

[loknathsingh]

@kahootali i am having around 15 deployment.yaml file and 23 configmap.yaml. so when we make any changes in a filebeat-configmap file then that changes get updated in Deployment file and filebeat pods Get restarted. but when we when we are making any changes in another configmap file of other service. then the pod related to that service should Restart but..its not happing...
so I would like to know that is there any solutio to restart The Pods whenever we make any changes in configmap.