Currently, Kubelet registers cAdvisor metrics through its own http server. That way, users who have authenticated to the kubelet can also access the prometheus metrics cAdvisor exports. It would be cool to have a way for CRI-O to do the same thing. Since it would have to be runtime agnostic, and likely implementation agnostic, it could be a CRI call that the kubelet requests at startup to get sockets and paths CRI-O wants to report