Comment 8 for bug 2012689

Please ignore `kubelet-eks.daemon[935]: cat: /var/snap/kubelet-eks/92/args: No such file or directory` Log output on my post.

This log occurred when creating an image from an EKS Ubuntu image using Packer.

In currently args was set from snap.

> cat /var/snap/kubelet-eks/104/args

--node-labels=instance-lifecycle=mixed,*=*,karpenter.sh/capacity-type=spot,karpenter.sh/provisioner-name=* --register-with-taints=dedicated=*:NoSchedule
--address="0.0.0.0"
--anonymous-auth=false
--authentication-token-webhook
--authorization-mode="Webhook"
--cgroup-driver="cgroupfs"
--client-ca-file="/etc/kubernetes/pki/ca.crt"
--cloud-provider="aws"
--cluster-dns="172.20.0.10"
--cluster-domain="cluster.local"
--config="/etc/kubernetes/kubelet/kubelet-config.json"
--container-runtime="remote"
--container-runtime-endpoint="unix:///run/containerd/containerd.sock"
--feature-gates="RotateKubeletServerCertificate=true"
--kubeconfig="/var/lib/kubelet/kubeconfig"
--max-pods="234"
--node-ip="*"
--pod-infra-container-image="602401143452.dkr.ecr.ap-northeast-2.amazonaws.com/eks/pause:3.5"
--register-node
--resolv-conf="/run/systemd/resolve/resolv.conf"

I'm interesting --register-with-taints was not return per args. However, there are times when it is registered normally, so this is not a problem, right?

---

After run manually "sudo systemctl restart snap.kubelet-eks.daemon", Node was registered normally.