What's new
HCL Universal Orchestrator is constantly evolving to offer you the most comprehensive orchestration capabilities. For known limitations, workarounds, and contact information of HCL Customer Support, see Release notes.
What is HCL Universal Orchestrator
HCL Universal Orchestrator is a cloud-native workload orchestration and scheduling platform built on Kubernetes. Its microservices-based architecture enables the centralized orchestration of multi-cloud and hybrid environments from a single point of control.
Deploying and Administrating
All the information you need to deploy and administrate HCL Universal Orchestrator.
Using the UI
The UI is the HCL Universal Orchestrator interface, from which you can design your scheduling environment and monitor every process.
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Orchestrating from Mobile
You can use your mobile devices to manage quickly and easily your whole HCL Universal Orchestrator environment.
Monitoring
Take your environment under control.
Using REST API
Use REST APIs to easily integrate workload scheduling capabilities with external products and solutions.
Uno AI Pilot
Welcome to the HCL Universal Orchestrator AI Pilot documentation. This resource is designed to guide you through everything you need to know about using UnO AI Pilot effectively. You will find detailed instructions, feature overviews, and helpful tips to ensure you get the best experience with UnO AI Pilot.
UnO Agentic AI Builder
- What is UnO Agentic AI Builder?
- Installation and Configuration
  This section guides you through installing the UnO Agentic AI Builder.
- Core Concepts
- UnO Agentic AI Builder Components
- Credential Library
- User Guide
- Tools Library
- Templates Library
- Best practices to Create Agents
- Troubleshooting UnO Agentic AI Builder
- Known Limitations
  This section outlines known limitations and constraints of the current release, helping users understand the boundaries of supported functionality and avoid unintended usage scenarios.
Troubleshooting
Recover your environment if any issue occurs.
Notices

CRDs Not Collected by apisix-ingress-controller

Issue: CRDs Not Collected by apisix-ingress-controller

If ApisixRoute, ApisixTls, or ApisixUpstream resources are not being picked up by the apisix-ingress-controller, consider the following troubleshooting steps:

Ingress Class Name Mismatch
Ensure that the ingressClassName specified in your Custom Resource Definition (CRD) resources precisely matches the value configured in the apisix-ingress-controller.
Resolution: Update the value of uno.agenticAIBuilder.common.apisix.ingressClassName to align with the controller's ingressClassName.
Namespace Label Missing (Namespace Selector in Use)

If the apisix-ingress-controller was deployed with a namespaceSelector, verify that the namespace where Agentic AI Builder is deployed is correctly labeled.

Resolution: The label on the namespace must match the one defined in the namespaceSelector configuration of the apisix-ingress-controller.
Missing Apisix Service for the Runner

This issue occurs if the Apisix service that should be associated with the runner component was not created.

Resolution: Restart the runner pod. The necessary service should be automatically created upon its restart.