👀 Views: 1886 💬 Answers: 1 📅 Created: 2025-06-13

kubernetes daemonset image-pull logging yaml

I'm confused about I'm trying to implement After trying multiple solutions online, I still can't figure this out... I'm working with an scenario where my DaemonSet pods are not updating on a node upgrade in my Kubernetes cluster running version 1.21. I have a DaemonSet configured to deploy a custom logging agent that pulls from an external container registry. However, after the node upgrade, the pods are exploring in a `CrashLoopBackOff` state because they want to find the container image. The relevant part of my DaemonSet configuration looks like this: ```yaml apiVersion: apps/v1 kind: DaemonSet metadata: name: logging-agent spec: selector: matchLabels: app: logging-agent template: metadata: labels: app: logging-agent spec: containers: - name: logging-agent image: myregistry.io/logging-agent:latest ports: - containerPort: 8080 volumeMounts: - name: var-log mountPath: /var/log volumes: - name: var-log hostPath: path: /var/log ``` The image is definitely present in the registry, and I verified that I can pull it manually on a different machine. I also ensured that the `imagePullSecrets` are correctly configured, yet I still see the following behavior in the pod logs: ``` behavior: ImagePullBackOff ``` I've tried deleting the DaemonSet and redeploying it, but it didn't resolve the scenario. Additionally, I checked the Kubernetes events and saw the following message: ``` Failed to pull image "myregistry.io/logging-agent:latest": rpc behavior: code = Unknown desc = behavior response from daemon: pull access denied for myregistry.io/logging-agent, repository does not exist or may require 'docker login' ``` I also confirmed that the Kubernetes nodes have access rights to the container registry. Can anyone guide to understand why the pods are not updating after the node upgrade and how to fix this scenario? My development environment is Windows. How would you solve this? What's the best practice here? Could someone point me to the right documentation?