Glen

@iwilltry42 When I ran the command your posted earlier, there was no such file or directory on my setup: ``` $ docker exec -it k3d-k3s-default-server-0 stat /usr/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/uds stat: cannot stat...

> There is no `nodeagent~uds` directory when I try to look inside the container: > > ``` > $ docker exec -ti k3d-k3s-default-server-0 ls -a /usr/libexec/kubernetes/kubelet-plugins/volume/exec > . .. >...

@lwr20 and I have looked into the `/usr/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/` directory inside the container. It contains the uds file ``` / # ls -l /usr/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/ total 4872 -r-xr-x--- 1 0 0 4987070...

I tried installing an older version of the operator and CRD (v3.15) on the k3d cluster. That was working so its possible the issue could be on our side. ```...

Upon further testing, our v3.21 (latest release) operator install seems to no longer be compatible with k3d clusters. I tested the operator starting from v3.15 and every version was working...