The built-in cri-docker integration relies on some legacy support (e.g., the docker-cadvisor integration) that a new CRI integration does not have. Below is a list of issues we need to address to fully support a non-builtin, non-docker container runtime via CRI.

A (potentially incomplete) list of issues to unblock adopting a (non-docker) CRI integration.

• Refactor kubelet to consume container metrics from CRI: CRI: instruct kubelet to (optionally) consume container stats from CRI #46984
• Refactor kubelet to consume image filesystem stats from CRI: CRI: Get ImageFS info for the runtime #33048
  - [ ] Providing cgroups for kubelet/cadvisor to track resource usage of CRI shim and container runtime stats: (see update in kubelet container runtime cgroup detection #30702)
• Authentication for the streaming server: [CRI] Add authentication to streaming server #36666
• Improve log format to handle logs: CRI: Define CRI log format better #44976

/cc @Random-Liu @feiskyer @mrunalp