Overview
Operator is a method for packaging, deploying, and managing Kubernetes applications, which can automate the entire lifecycle of applications, such as creation, update, and deletion.
Platform administrators can deploy the Operator in OperatorHub on a cluster basis.
Related concepts
-
OperatorHub: A network console that presents a list of existing Operators on the platform. Through OperatorHub, platform administrators can view Operator descriptions, detailed information, and install and manage Operators.
-
Resources: CRD (CustomResourceDefinition) resources owned by the Operator. In the Kubernetes API, CRD resources are endpoints for storing collections of API objects (CR, Custom Resource) of a certain type.
-
Custom Resources: CR objects are specific types of API objects created by CRDs owned by Operators deployed in the cluster. After the Operator is successfully installed in the cluster, users in all projects associated with the cluster can add CRs to the namespace.
-
Resource Instances: Resource instances created in a namespace by calling Kubernetes API based on CR, which can provide the ability of Operator for the namespace by creating resource instances.
Operator usage notes
Currently, there are four types of Operator sources in the platform OperatorHub. The technical support scope provided by the platform varies for Operators from different sources, and corresponding evaluations should be done before use.
| Supplier Type | Usage Notes |
|---|---|
| Custom | Uploaded by users themselves. The stability is unknown, and caution should be exercised when using it. If there are any problems during use, please contact the author for help. |
| Community | From the open source community. Not checked or verified by the platform. If there are any problems during use, please contact the open source community for help. |
| Certified | Provided by the platform or third parties. The platform has checked and verified it, but does not promise a service level agreement (SLA). If there are any problems during use, please contact the provider for help. |
| Platform | Independently developed by the platform and guaranteed for security and availability. |
StorageClasses supported by Operator
| Operator | TopoLVM | local-path | Ceph | NFS Shared Storage |
|---|---|---|---|---|
| MySQL PXC | Supported | Supported | - | - |
| MySQL MGR | Supported | Supported | - | - |
| Kafka | Supported | Supported | Supported | Supported |
| Redis | Supported | - | Supported | Supported |
| RabbitMQ | Supported | - | Supported | - |
| PostgreSQL | Supported | Supported | Supported | - |
Default scheduling rules for instances
| Component | Default scheduling rule (single instance) |
|---|---|
| MySQL PXC | Only one MySQL node can be scheduled on each node at most (required). |
| MySQL MGR | Only one MySQL node can be scheduled on each node at most (required). |
| Kafka | Only one Broker node can be scheduled on each node at most (required). |
| Redis |
|
| RabbitMQ | Only one RabbitMQ node can be scheduled on each node at most (required). |
| PostgreSQL | Only one PostgreSQL node can be scheduled on each node at most (required). |