Deploy the Operator

To deploy an Operator in a specified cluster or namespace, allowing developers and testers to use the Operator to create and manage instances.

Note: This section provides basic operation instructions. Different operators may have different requirements, so please follow the actual situation to complete the operation.

precautionary

• In an IPv6 environment, the repository (i.e., global registry) used by the Operator needs to be configured with a domain name and support IPv6 resolution. Otherwise, the application will not be able to be displayed in the app store.

• If an Operator upgrade is blocked by an OperatorCondition, the Operator’s status will be marked as Blocked. OperatorCondition is a custom resource used to define specific states or conditions that can trigger specific actions.

• Operators within the same namespace support only a single upgrade strategy. If both Manual and Auto upgrade strategies are present simultaneously, all Operators will be uniformly changed to Manual upgrade strategy.

• If there are Operators with a Manual upgrade strategy in the namespace, subsequent Operator deployments will require two manual confirmations to complete the deployment.

• If multiple pending Operators exist in the same namespace, once one Operator confirms deployment, the other pending Operators will also be automatically confirmed and deployed.

Procedure of operation

1. On the left navigation bar, click Catalog > Operators.

2. On the OperatorHub tab, click on the Deployments in the Operator card.

3. Configure relevant parameters.

   Parameter	Description
   Upgrade Strategy	Automatic: When a new version of the Operator is available, it will be automatically upgraded by the Operator Lifecycle Manager (OLM) without manual intervention. Manual: When a new version of the Operator is available, it requires manual upgrading. Note: This setting only affects the Operator and does not involve the instances managed by the Operator. When the Operator developer specifies an upgrade strategy, users cannot change the upgrade strategy for this Operator in the deployment UI. To change the upgrade strategy, modify the corresponding YAML configuration file.
   Deployment Mode	Cluster: All namespaces under the cluster share a single Operator for instance creation and management. Note: Due to issues with the Single Namespace and Multi-Namespace modes, only the Cluster mode is supported in the new version.
   Channel	Different upgrade paths provided by the Operator developer based on the Operator version characteristics, such as alpha and beta, preview and stable. Once a channel is selected and an upgrade is triggered, the platform will upgrade the Operator to the latest version in that channel.
   Namespace	Recommended Namespace: When the Operator developer sets a Recommended Namespace, it is selected by default. It is strongly recommended that users deploy the Operator directly in the recommended namespace. If the Recommended namespace resource does not exist, it will be automatically created upon deployment. Select Namespace: When the Operator developer has not set a Recommended Namespace, this option is selected by default. Users can freely select the namespace in which they wish to deploy the Operator as needed. Note: To ensure platform stability, certain platform-specific namespaces are hidden and users cannot deploy Operators in these namespaces. To avoid conflicts with upgrade strategies, try not to deploy multiple Operators to the same namespace.

   Note:

   • Click on YAML in the upper right corner of the page to supplement the Subscription Config information with a YAML file, such as targeted deployment, taint toleration, resource quotas, etc. After deploying the Operator, you can edit or delete the subscription information, refer to Subscription Management .

   • Configuration examples

     config:
      nodeSelector:
          beta.kubernetes.io/arch: amd64
      tolerations:
          - key: "node.alpha.kubernetes.io/unreachable"
            operator: "Exists"
            effect: "NoExecute"
            tolerationSeconds: 6000

4. Click on Deployments.

5. If the manual upgrade strategy is selected, you also need to complete the deployment according to the prompts on the Operator details page.

   Note: When a new version of the Operator is released, you can find the Operator under the Deployed Operators list and manually upgrade it.

What’s next

Once the Operator is successfully deployed, you can start using the Operator , or remind developers and testers to go to the App Store to create applications.