Questão de Container Orchestration #019e3a4f

In Kubernetes, the component responsible for running containers is the container runtime interface (CRI) implementation, such as CRI-O. CRI-O is a lightweight container runtime that allows Kubernetes to run containers using OCI-compliant runtimes like runc. It acts as an intermediary between the kubelet and the container runtime, handling container lifecycle operations.

How it Works

The kubelet on each node communicates with the container runtime via the CRI (Container Runtime Interface) API. CRI-O implements this interface, enabling Kubernetes to manage containers without relying on Docker. It pulls images, creates and starts containers, and monitors their status.

Why CRI-O is Correct

CRI-O is specifically designed to be a Kubernetes-native container runtime. It directly supports the CRI, making it the component that runs containers in a Kubernetes cluster.

Why Other Options are Incorrect

• etcd: This is a distributed key-value store used for storing cluster state and configuration data, not for running containers.
• cloud-controller-manager: This component manages cloud-specific resources like load balancers and storage volumes, but does not run containers.
• kube-controller-manager: This runs controller processes that handle replication, endpoints, and other cluster-level functions, but it does not directly run containers.