Home > Storage > ObjectScale and ECS > Product Documentation > Dell ObjectScale: Overview and Architecture > Operators
The Kubernetes operator pattern is used throughout ObjectScale. An operator is an application-specific controller that contains all the operational considerations of an application. Operator resources are defined in YAML files as Kubernetes Custom Resource Definitions (CRDs). Custom resources define actions available to users of the operator. The following table describes ObjectScale operators:
Operator | Description |
Atlas operator | Provides Atlas services to provide better efficiency through key-value operations, system operations overhead, and overall CPU and memory use. |
ObjectScale licensing | Performs capacity monitoring. |
ObjectScale manager | Installs and manages custom ObjectScale resources. |
ObjectScale monitoring | Records and presents metrics. ObjectScale monitoring is a suite of services. |
ObjectScale operator | Manages object stores as a Kubernetes construct through run-time orchestration. Dynamic reconfiguration is based on external cluster and failure conditions. ObjectScale operator can handle multistage operations, such as create, upgrade, expand. |
ObjectScale service procedure | Orchestrates service-oriented tasks such as temporary maintenance mode, disk replacements, object store expansions, and upgrades. |
Object store | Provides isolated tenant object storage. |
ZooKeeper | Used in the object store as part of the services discovery mechanism. A ZooKeeper cluster is deployed for each object store by the ZooKeeper operator. |
ObjectScale supports the following service procedures that customers can use to maintain the ObjectScale deployment: