when a pod is created, the name of the systemd slice assigned to the pod looks like

/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod15778196_6e1f_4b5d_8012_12c7bf5c04b3.slice/crio-4015cec33e493690b48385efa86af20938e5b80077094cbc5e875945178d57be.scope

Version-Release number of selected component (if applicable): 4.19   

    Always

    1. Create a pod with one container
    2. oc debug node/<node-where-the-pod-is-running> && chroot /host
    3. Get the ID of the container: crictl ps | grep <pod-name>
    4. Get the PID of the container: crictl inspect <container-id> | grep pid
       # crictl inspect 8c457293e0cd4 | grep pid
       "pid": 1603462,
    5. cat /proc/<PID>/cgroup
    

    0::/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod96e849af_6a38_4fe3_b701_567ec3a1515d.slice/crio-8c457293e0cd4929fa1c2beb664b85bd7a2ff430d9ceeee083c1b28eca3318bc.scope

    0::/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod-96e849af_6a38_4fe3_b701_567ec3a1515d.slice/crio-8c457293e0cd4929fa1c2beb664b85bd7a2ff430d9ceeee083c1b28eca3318bc.scope

Note the `-` betwen pod and 96e849af.....

    This is not more than informational and perhaps helpful only to ease gathering the UUID of a pod given a PID of a process running in it from the /proc FS.