A public-health team labels every Deployment an “Operator” because it runs in the cluster. What distinction should architects enforce?
Select an answer to reveal the explanation.
Short Explanation
Calling every Deployment an operator is like calling every city van an ambulance. Operators specifically watch custom resources and reconcile them. A plain web Deployment is just a workload unless it implements that controller pattern.
Full Explanation
In Kubernetes usage, an operator is a controller—often packaged as a Deployment—that manages application or infrastructure state via custom resources and reconcile logic. Not every Deployment is an operator; the defining behavior is CR-centric control, not merely existing as a workload object.