Skip to main content
Version: Release 24.1

Upgrade Options Reference for Digital.ai Release Runner

  • Here's a list of questions that you would have to answer to upgrade Digital.ai Release Runner using the xl kube upgrade command.
  • You must select one of the available options for some of the questions.
  • Use the arrow keys to move up or down and press enter to select an option.

Release Upgrade Options Reference

Here's a list of questions that you would have to answer to upgrade Digital.ai Release or Runner using the xl kube upgrade command.

Here's the list of questions

Confirm the kubectl Context

Prompt? Following kubectl context will be used during execution: <kubectl-context/username>? (Y/n)
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valueskubectl current context
Default valuekubectl current context
RemarksConfirm the kubectl context to proceed.

Choose a Kubernetes Platform

Prompt? Select the Kubernetes setup where the Digital.ai Devops Platform will be installed, updated or cleaned:
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesOpenshift [Openshift]
AWSEKS [AWS EKS]
PlainK8s [Plain multi-node K8s cluster]
AzureAKS [Azure AKS]
GoogleGKE [Google Kubernetes Engine]
Default valueOpenshift [Openshift]
RemarksYou must have your cluster ready before you select an answer for this prompt.

Choose a Kubernetes Namespace

Prompt? Do you want to use an custom Kubernetes namespace (current default is digitalai): [? for help] (y/N)
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valuedigitalai
RemarksType the name of a custom namespace where you want to install or upgrade Release or go with the default namespace, which is digitalai.

Choose the Product to Upgrade

Prompt? Product server you want to perform upgrade for [Use arrows to move, enter to select, type to filter, ? for more help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesdai-release [Digital.ai Release with optional Runner]
dai-deploy [Digital.ai Deploy]
dai-release-remote-runner [Release Runner for Digital.ai Release]
Default valuedai-release [Digital.ai Release with optional Runner]
RemarksSelect a product—dai-release-remote-runner [Release Runner for Digital.ai Release]

Select Type of Image Registry

Note: You can choose a custom public or private registry, which can be used to perform the setup of Deploy from a custom image registry and image repository. For more information, see Setup Custom Image Registry

PromptSelect type of image registry (current default is default): [? for help] (xebialabs)
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valuedefault
RemarksType the image repository. It is recommended to go with the default, which is xebialabs.

Enter the Release Runner Repository Name

Prompt? Enter the Release Runner repository name (eg: <repositoryName> from <repositoryName>/<imageName>:<tagName>): [? for help] (xebialabs)
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valuexebialabs
RemarksType the repository name. It is recommended to go with the default, which is xebialabs

Enter the Release Runner Image Name

Prompt? Enter the Release Runner image name (eg: <imageName> from <repositoryName>/<imageName>:<tagName>): [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesrelease-remote-runner
Default valuerelease-remote-runner
RemarksType the name of the image you want to use for installation.

Enter the Release Runner Image Tag

The xl kube install and xl kube upgrade options reference let you go with the default (latest) docker image tags available when you install or upgrade Digital.ai Release or Runner. However, here are the Docker Hub links to verify all the available image tags.

Prompt? Enter the Release Runner image tag (eg: <tagName> from <repositoryName>/<imageName>:<tagName>): [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valueThe latest Release Runner is available in the repository, for example, 24.1.2
RemarksType the product version number you want to install, for example, 23.3.3 or 24.1.2.

Enter the Release Runner Helm Chart release name

Prompt? Enter the Release Runner Helm Chart release name: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valueremote-runner
RemarksEnter the Release Runner helm chart release name.

Source of the Release Runner Helm Chart

Prompt? Use default version of the Release Runner helm chart: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesYes/No
Default valueYes
RemarksIf selected Yes it is using the Release Runner provided with blueprints. If No you need to download the helm chart and reference through the path in the next question.

Enter the Release Runner Helm Chart path

Prompt? Enter the Release Runner Helm Chart path (URL or local path): [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valueNA
RemarksEnter the local file system path of Helm chart for the Release runner or the URL of the Release Runner Helm Chart package.

Enter the Release URL used by Release Runner

Prompt? Enter the Release URL that will be used by the Release Runner: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valueNA
RemarksEnter the Release URL that will be used by Release runner.

Enter the Release Token used by Release Runner

Note: This question is asked during the installation process, and you already have a Release instance running, you will need to create a Personal Access Token on the Release.

Prompt? Enter the Release Token that will be used by Release Runner: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default valueNA
RemarksEnter the Release Token that will be used by Release runner.

Enter the Release Runner replica count

Prompt? Enter the Release Runner replica count: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesNA
Default value1
RemarksEnter the Release Runner replica count.

Enable truststore for Release Runner

Prompt? Enable truststore for Release Runner: [? for help]
Prompt valid for—platformEKSAKSGKEOpenShift on AWSPlain Multi-node Kubernetes
Cluster On-premise
YesYesYesYesYes
Available valuesYes/No
Default valueNo
RemarksEnable truststore for Release Runner.

Once you are done answering the questions, the installer then proceeds with the upgrade by applying the resources to the cluster and completes the upgrade.