On Kubernetes RKE2 1.32.11 (presumably many other versions as well) on Ubuntu 22.04.5 with kernel 6.8.0-90-generic, psc isn't picking up any of the container.X fields, they are simply empty. All other fields appear to be populated just fine, at least the ones I have tested.
I've tested on a functional cluster, and crictl works well as you can see from the below sample.
runtime-endpoint: unix:///run/k3s/containerd/containerd.sock
CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID POD NAMESPACE
f6729c4359f35 bc23176db8307 2 weeks ago Running kube-flannel 1 64d017e046740 rke2-canal-k8c7t kube-system
21dff395cd1d4 6d4ff648e9d06 2 weeks ago Running calico-node 1 64d017e046740 rke2-canal-k8c7t kube-system
1eef80267b8fb 5b845bb4ae0a7 2 weeks ago Running kube-apiserver 1 af8e0d5293fac kube-apiserver-k8s-t01-c01 kube-system
81a8b6fe6afa8 5b845bb4ae0a7 2 weeks ago Running kube-proxy 0 4dbb8e91a570e kube-proxy-k8s-t01-c01 kube-system
59880ccb7a6b7 89c661380636c 2 weeks ago Running etcd 1 fe851b8747fe2 etcd-k8s-t01-c01
psc is a cool and useful tool, thanks for creating this :-)
On Kubernetes RKE2 1.32.11 (presumably many other versions as well) on Ubuntu 22.04.5 with kernel 6.8.0-90-generic, psc isn't picking up any of the container.X fields, they are simply empty. All other fields appear to be populated just fine, at least the ones I have tested.
I've tested on a functional cluster, and crictl works well as you can see from the below sample.
psc is a cool and useful tool, thanks for creating this :-)