Bitzu

KCNA ยท Cloud native ecosystem and community

Why do OCI, CRI, CNI and CSI matter?

OCI, CRI, CNI, CSI, vendor neutrality and why standards matter.

Key points

  • They are open interfaces that keep Kubernetes vendor neutral.
  • OCI defines the container image and runtime formats.
  • CRI is how the kubelet talks to a container runtime.
  • CNI is the plugin interface for pod networking.
  • CSI is the interface for storage drivers.
  • Because the interfaces are standard, you can swap an implementation without changing the rest of the stack.

Source: https://github.com/opencontainers/image-spec

Practice questions

Single choice

Which interface lets the kubelet communicate with a container runtime?

  1. CNI
  2. CSI
  3. CRI
  4. OCI
Show answer

Answer: C. CRI

CRI, the Container Runtime Interface, is the kubelet-to-runtime API. CNI covers networking, CSI storage, and OCI the image and runtime formats.

Select all that apply

Which interface-to-purpose pairs are correct?

  1. CNI - pod networking plugins
  2. CSI - storage drivers
  3. CRI - container runtimes
  4. OCI - network policy enforcement
  5. CSI - container image format
Show answer

Answer: A. CNI - pod networking plugins, B. CSI - storage drivers, C. CRI - container runtimes

CNI is for pod networking, CSI for storage and CRI for runtimes. OCI is not a networking interface and CSI is not about images.

True or false

True or false: an OCI image can only run on a runtime built by the same vendor that created the image tool.

Show answer

Answer: False

False. The point of the OCI specs is portability: any compliant runtime can run a compliant image.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More KCNA topics in this module