Deploying HCL Universal Orchestrator

Deploying HCL Universal Orchestrator requires the deployment of all its microservices, the UI, the cloud agent, and optionally, the Orchestration CLI.

Before starting the deployment, make sure all the following mandatory prerequisites are met:

Prerequisites

Deploy a Kubernetes cluster at version 1.29 or later with access configured using Kubectl at version 1.29.4 or later
Install Helm at version 3.12 or later
Install one of the following streaming data platforms: Apache Kafka at version 3.4.0 or later or Redpanda at version 23.11 or later
Deploy one of the following databases:
- MongoDB
- Azure Cosmos DB for MongoDB (vCore)
- DocumentDB for AWS deployment
Deploy an OIDC provider.
Create the wauser on the OIDC provider.
Optionally, deploy cert-manager to manage certificates. This step is strongly recommended.

Note: To monitor the metrics of your workload, you can install any data scraping and interactive analysis platform.

Deploying

After all prerequisites are met, you can proceed with the following deployment steps:

Create a namespace, using the command:
```
 kubectl create namespace <uno_namespace>
```
Create a secret to authenticate to the repository and download the images.
Deploy the product components:
1. Log into the Helm registry using the command:
```
 helm registry login hclcr.io  
```
2. Pull the Helm chart using the command:
```
 helm pull oci://hclcr.io/uno/hcl-uno-chart
```
  Note: To download a specific version of the Helm chart, use the --version option in the helm pull command.
3. You can customize the deployment by adjusting the values in the values.yaml file, which contains a detailed explanation for each parameter. You can find the values.yaml file here.
Download and configure the HCL UnO agent as explained in Installing HCL UnO agent.
Optionally, download and configure the Orchestration CLI, as explained in Configuring the Orchestration CLI.

Note: If you plan to make your service accessible from the Internet, it is recommended you set up a firewall to prevent Denial Of Service (DOS) attacks.

For complete information about prerequisites and procedures for deploying, configuring, and uninstalling HCL Universal Orchestrator, see HCL Universal Orchestrator readme file.

Optionally, you can install agents at HCL Workload Automation, version 10.2.3 to be able to manage all task integrations. For more information, see Installing and connecting HCL Workload Automation dynamic agent at version 10.2.3.

Optionally, to enable UnO AI Pilot, set global.enableUnoAIPilot to true in the values.yaml deployment file.

You can also install a separate package containing the Orchestration CLI, which enables command-line interface interactions with HCL Universal Orchestrator. You can install the Orchestration CLI on any workstation in your HCL Universal Orchestrator environment. For more information, see Installing and authenticating the Orchestration CLI.

To further extend the capabilities, you can configure HCL UnO agent, an on premises agent that can run all types of tasks. For more information, see Installing HCL UnO agent.