Kubernetes Container Orchestration Operators and Custom Resources

Question 1

What is a Custom Resource Definition (CRD) in Kubernetes?

Accepted Answer

An extension mechanism that allows defining new resource types in the Kubernetes API

Answer

CRDs extend the Kubernetes API by allowing users to define and manage their own custom resource types beyond the built-in ones.

Question 2

What is the primary purpose of a Kubernetes Operator?

Accepted Answer

To automate the management of complex stateful applications using domain-specific knowledge

Answer

Operators encode operational knowledge into software that automates the full lifecycle management of complex applications.

Question 3

Which API group is used for managing Custom Resource Definitions?

Accepted Answer

apiextensions.k8s.io/v1

Answer

CRDs are managed through the apiextensions.k8s.io/v1 API group, which handles extensions to the Kubernetes API itself.

Question 4

What is a controller in the Kubernetes operator pattern?

Accepted Answer

A reconciliation loop that watches resources and takes actions to match desired state

Answer

Controllers implement a reconciliation loop that continuously watches resource state and takes actions to converge actual state with desired state.

Question 5

Which tool is the official framework for scaffolding and building Kubernetes Operators?

Accepted Answer

Operator SDK

Answer

The Operator SDK, part of the Operator Framework project, provides scaffolding, libraries, and tooling for building Kubernetes Operators.

Kubernetes Container Orchestration Practice Test