DaemonSet example is not working in Macbook

[imShakil]

This following DaemonSet example is not working in Macbook:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/

❯ kubectl -n kube-system get ds
NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
fluentd-elasticsearch   1         1         0       1            0           <none>                   4m14s
kube-proxy              1         1         1       1            1           kubernetes.io/os=linux   21d

❯ kubectl -n kube-system get pods -o wide
NAME                               READY   STATUS             RESTARTS      AGE     IP             NODE       NOMINATED NODE   READINESS GATES
coredns-668d6bf9bc-tmzfp           1/1     Running            4 (45h ago)   21d     10.244.0.36    minikube   <none>           <none>
coredns-668d6bf9bc-zq9jt           1/1     Running            4 (45h ago)   21d     10.244.0.35    minikube   <none>           <none>
etcd-minikube                      1/1     Running            4 (45h ago)   21d     192.168.49.2   minikube   <none>           <none>
fluentd-elasticsearch-rqpdx        0/1     ImagePullBackOff   0             4m32s   10.244.0.79    minikube   <none>           <none>

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[shurup]

Can you please run kubectl describe pod -n kube-system fluentd-elasticsearch? In my quick test, I see the following output:

  Type     Reason     Age                     From               Message
  ----     ------     ----                    ----               -------
  Normal   Scheduled  8m15s                   default-scheduler  Successfully assigned kube-system/fluentd-elasticsearch-5tv66 to minikube
  Normal   Pulling    4m52s (x5 over 8m15s)   kubelet            Pulling image "quay.io/fluentd_elasticsearch/fluentd:v2.5.2"
  Warning  Failed     4m48s (x5 over 8m10s)   kubelet            Failed to pull image "quay.io/fluentd_elasticsearch/fluentd:v2.5.2": [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of quay.io/fluentd_elasticsearch/fluentd:v2.5.2 to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
  Warning  Failed     4m48s (x5 over 8m10s)   kubelet            Error: ErrImagePull
  Warning  Failed     2m59s (x19 over 8m10s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    2m30s (x21 over 8m10s)  kubelet            Back-off pulling image "quay.io/fluentd_elasticsearch/fluentd:v2.5.2"

If that's your case as well, updating the fluentd image version from quay.io/fluentd_elasticsearch/fluentd:v2.5.2 to quay.io/fluentd_elasticsearch/fluentd:v5.0.1 in the manifest (controllers/daemonset.yaml) should fix the issue. Please confirm on your side. If that's true, we'll just need to update this version in the listing provided in the docs.

[imShakil]

Hi, @shurup

Yes, It was a version issue. I have updated image version to this: quay.io/fluentd_elasticsearch/fluentd:v5.0.1 and its working now.

❯ kubectl get pods -n kube-system
NAME                               READY   STATUS    RESTARTS      AGE
coredns-668d6bf9bc-tmzfp           1/1     Running   5 (19h ago)   25d
coredns-668d6bf9bc-zq9jt           1/1     Running   5 (19h ago)   25d
etcd-minikube                      1/1     Running   5 (19h ago)   25d
fluentd-elasticsearch-rfl8z        1/1     Running   0             80m
kube-apiserver-minikube            1/1     Running   5 (19h ago)   25d
kube-controller-manager-minikube   1/1     Running   5 (19h ago)   25d
kube-proxy-mnhmk                   1/1     Running   5 (19h ago)   25d
kube-scheduler-minikube            1/1     Running   5 (19h ago)   25d
metrics-server-7fbb699795-vvqbk    1/1     Running   2 (19h ago)   6d1h
storage-provisioner                1/1     Running   9 (19h ago)   25d

❯ kubectl get ds -n kube-system
NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
fluentd-elasticsearch   1         1         1       1            1           <none>                   86m
kube-proxy              1         1         1       1            1           kubernetes.io/os=linux   25d

I would love to contribute I don't know where the manifest file is located.
Thanks.

[shurup]

@imShakil perfect! Thanks for your feedback and willingness to contribute! Surely, you're most welcome to make it.

The manifest in charge is the daemonset.yaml file located in this directory. However, since we have the same issue with fluentd:v2.5.2 being mentioned in fluentd-daemonset.yaml and fluentd-daemonset-update.yaml files next to it (in the same directory), I kindly ask you to modify those files as well in the same PR you'll raise.

[reylejano]

fixed with #51626
/close

[k8s-ci-robot]

@reylejano: Closing this issue.

In response to this:

fixed with #51626
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.