Cilium status exhibitBased on the cilium status output above, what is correct about the Cilium...

Technical explanation

The status output reports Operator: OK , followed by Deployment cilium-operator Desired: 1, Ready: 1/1, Available: 1/1 . This establishes that the Cilium Operator is deployed and healthy, making B the intended answer. Cilium uses Kubernetes CustomResourceDefinitions as its default mechanism for storing and propagating cluster state, while the operator performs cluster-wide duties that should be handled once centrally rather than independently on every node.

Option A is contradicted by the exhibit: both hubble-ui and hubble-relay appear as ready deployments and running containers. Option C is incorrect because the resource is explicitly identified as a Deployment ; the cilium agents, by contrast, are shown as a DaemonSet . Option D incorrectly treats the displayed desired replica count as a permanent restriction. A desired count of one describes this installation’s current configuration, not a universal maximum.

The exhibit also shows embedded Envoy mode and three healthy Cilium agent instances, but neither detail changes the operator conclusion.

Official references

Cilium Component Overview , Setting up Hubble Observability

Study Guide topic: Cilium components, Cilium Operator, CRD-backed state, and status interpretation.