While parsing /proc/self/cgroup to obtain the containerId, it's possible there is a .scope postfix, such as crio-736665661f3cf3ec691b2feeb2a1ec78918c0ef65381160bbb04f4c298169679.scope which breaks our current parser.
Testing
Tested in openshift and gke clusters
Checklist:
[X ] My changes generate no new warnings
[X ] I have added tests that prove my fix is effective or that my feature works
[X ] Any dependent changes have been merged and published in downstream modules
Description
While parsing /proc/self/cgroup to obtain the containerId, it's possible there is a
.scopepostfix, such ascrio-736665661f3cf3ec691b2feeb2a1ec78918c0ef65381160bbb04f4c298169679.scopewhich breaks our current parser.Testing
Tested in openshift and gke clusters
Checklist: