- Getting Started
- Network requirements
- Single-node requirements and installation
- Multi-node requirements and installation
- Post-installation
- Accessing AI Center
- Provision an AI Center tenant
- Updating Orchestrator and Identity Server certificates
- Resizing PVC
- Adding a new node to the cluster
- ML packages offline installation
- Configuring the cluster
- Configuring the FQDN post-installation
- Backing up and restoring the cluster
- Using the monitoring stack
- Setting up a Kerberos authentication
- Provisioning a GPU
- Using the configuration file
- Node scheduling
- Migration and upgrade
- Basic Troubleshooting Guide
Accessing AI Center
The general-use AI Center user interface serves as a portal for both organization administrators and organization users. It is a common organization-level resource from where everyone can access all of your Automation Suite areas: administration pages, platform-level pages, service-specific pages, and user-specific pages.
To access AI Center, take the following steps:
- Go to the following URL:
https://${CONFIG_CLUSTER_FQDN}/ai-app
. - Switch to the Host organization.
- Connect to the host tenant using the admin user.
- A list of tenants for your Orchestrator is displayed. Enable AI Center on the desired tenant by clicking on ⁝ (three-dot button) and then provision (provisioning will take a few seconds).
- Log out and log in the provisioned tenant.
https://objectstore.${CONFIG_CLUSTER_FQDN}
url once with every browser that you want to use in order to be able to interact with storage.
Before running any kubectl commands, make sure to enable kubectl. This allows you to run commands for retrieving passwords and configuration details for the cluster.
To enable kubectl, run the following command:
sudo su -
export KUBECONFIG="/etc/rancher/rke2/rke2.yaml" \)\)
&& export PATH="$PATH:/usr/local/bin:/var/lib/rancher/rke2/bin"
sudo su -
export KUBECONFIG="/etc/rancher/rke2/rke2.yaml" \)\)
&& export PATH="$PATH:/usr/local/bin:/var/lib/rancher/rke2/bin"
You can use the ArgoCD console to manage installed products.
To access ArgoCD, take the following steps:
- The URL is the following:
https://alm.${CONFIG_CLUSTER_FQDN}
. - The username is admin.
-
To access the password, run the following command:
kubectl get secrets/argocd-admin-password -n argocd \)\) -o "jsonpath={.data['password']}" | base64 -d
kubectl get secrets/argocd-admin-password -n argocd \)\) -o "jsonpath={.data['password']}" | base64 -d
ArgoCD is accessible at:
https://alm.<LB DNS>
https://alm.<LB DNS>
true
.
Automation Suite uses Rancher to provide cluster management tools out of the box. This helps you manage the cluster and access monitoring and troubleshooting.
See Rancher documentation for more details.
To access the Rancher console, take the following steps:
- Go to the following URL:
https://monitoring.${CONFIG_CLUSTER_FQDN}
. - The username is admin.
- To access the password, run the following
command:
kubectl get secrets/rancher-admin-password -n cattle-system \)\) -o "jsonpath={.data['password']}" | base64 -d
kubectl get secrets/rancher-admin-password -n cattle-system \)\) -o "jsonpath={.data['password']}" | base64 -d
The installer automatically generates and configures a self-signed certificate. This generates a warning in the browser when navigating to the installed products and expires in 3 months.
We recommend installing a certificate obtained from a certificate authority.
To retrieve the current certificates, run the following command:
kubectl get secrets/istio-ingressgateway-certs -n istio-system -o "jsonpath={.data['ca\)\).crt']}" | echo $(base64 -d) >ca.cer
kubectl get secrets/istio-ingressgateway-certs -n istio-system -o "jsonpath={.data['tls\)\).crt']}" | echo $(base64 -d) > tls.cer
kubectl get secrets/istio-ingressgateway-certs -n istio-system -o "jsonpath={.data['ca\)\).crt']}" | echo $(base64 -d) >ca.cer
kubectl get secrets/istio-ingressgateway-certs -n istio-system -o "jsonpath={.data['tls\)\).crt']}" | echo $(base64 -d) > tls.cer