Reloader not seeing changes

[Thomas Schaaf]

I am using the latest version of the helm chart to deploy reloader. I have the following values:

# https://github.com/stakater/Reloader/blob/master/deployments/kubernetes/chart/reloader/values.yaml
fullnameOverride: reloader
reloader:
  deployment:
    replicas: 1
    resources:
      limits:
        cpu: "100m"
        memory: "512Mi"
      requests:
        cpu: "10m"
        memory: "128Mi"
    priorityClassName: system-cluster-critical
    securityContext:
      runAsNonRoot: true
      runAsUser: 65534
    containerSecurityContext:
      capabilities:
        drop:
          - ALL
      allowPrivilegeEscalation: false
      readOnlyRootFilesystem: true
  service:
    port: 9090
  serviceMonitor:
    enabled: true
    namespace: reloader

In my deployment in another namespace I have added the annotation:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: ingress-nginx-controller
  namespace: ingress-nginx
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/managed-by: kustomize
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.7.0
    helm.sh/chart: ingress-nginx-4.6.0
    kustomize.toolkit.fluxcd.io/name: ingress-nginx
    kustomize.toolkit.fluxcd.io/namespace: flux
  annotations:
    deployment.kubernetes.io/revision: '16'
    reloader.stakater.com/auto: 'true'
[...]

When starting reloader I see the following logs:

time="2023-04-25T10:01:53Z" level=info msg="Environment: Kubernetes"
time="2023-04-25T10:01:53Z" level=info msg="Starting Reloader"
time="2023-04-25T10:01:53Z" level=warning msg="KUBERNETES_NAMESPACE is unset, will detect changes in all namespaces."
time="2023-04-25T10:01:53Z" level=info msg="created controller for: configMaps"
time="2023-04-25T10:01:53Z" level=info msg="Starting Controller to watch resource type: configMaps"
time="2023-04-25T10:01:53Z" level=info msg="created controller for: secrets"
time="2023-04-25T10:01:53Z" level=info msg="Starting Controller to watch resource type: secrets"

After changing configmaps I do not see any logs.

How can I verify why no changes are detected?

[Thomas Schaaf]

The issue seems to be that ingress-nginx does not mount the config map normally and I had believer all configmap changes would be logged in the output. Everything seems to work with other deployments.

[sdwerwed]

@thomaschaaf I have same issue with bitnami fluentd, you can reopen the issue because id it is still relevant with ingress.