Airgap Pre-built Kubernetes (K8s) Install

Make sure your K8s cluster is ready for Arthur platform installation by following the K8s preparation guide.

Prepare your private container image registry for Arthur artifacts by creating the following list of repositories:

Admin Console:

arthurai/dex
arthurai/kotsadm
arthurai/kotsadm-migrations
arthurai/local-volume-fileserver
arthurai/local-volume-provider
arthurai/minio
arthurai/postgres

Application:

arthurai/alert-service
arthurai/alpine
arthurai/api-service
arthurai/argocli
arthurai/argoexec
arthurai/aws-cli
arthurai/busybox
arthurai/clickhouse-backup
arthurai/clickhouse-operator
arthurai/clickhouse-server
arthurai/client
arthurai/cp-kafka-connect
arthurai/cp-schema-registry
arthurai/cp-server
arthurai/cp-zookeeper
arthurai/curl
arthurai/custom-hpa
arthurai/dataset-service
arthurai/enrichment-helpers
arthurai/inference-consumer
arthurai/ingestion-service
arthurai/jmx-prometheus-exporter
arthurai/k8s-prometheus-adapter-amd64
arthurai/kafka-connect
arthurai/kafka-connect-monitor
arthurai/kafka-exporter
arthurai/kafka-prometheus-jmx-exporter
arthurai/kubectl
arthurai/mc
arthurai/metric-service
arthurai/metrics-exporter
arthurai/minideb
arthurai/minio
arthurai/model-server
arthurai/model-server-controller
arthurai/postgresql
arthurai/python-jobs
arthurai/pytorch-jobs
arthurai/query-service
arthurai/redis
arthurai/scala-spark-jobs
arthurai/schema-service
arthurai/workflow-controller
arthurai/zookeeper
arthurai/zookeeper-exporter

As an example, here’s how you can create a new arthurai/alert-service repository on AWS ECR.

export AWS_REGION=<your_region>
aws ecr create-repository --repository-name=arthurai/alert-service

Go to the download portal using the URL and the password provided by Arthur.

Select the “Bring my own cluster” option. .png image

Click the “Download license” button to download your license in YAML file.

Download the “Latest Kots Admin Console Airgap bundle” and the “Latest Arthur Airgap bundle”.

Make sure you’re in the correct kubectl environment context before running the installer.

Install the KOTS kubectl extension on your local machine:

curl https://kots.io/install | bash

If the Linux workstation you’re running kubectl from is also in the airgap environment, download the “Latest Kots CLI” from the download portal and install it like below:

tar zxf kots_linux_amd64.tar.gz
# move it to a location that's on your path
sudo mv kots /usr/local/bin/kubectl-kots

Note that the KOTS CLI and “Latest Kots Admin Console Airgap bundle” must be installed at the same time and therefore on the same version.

If your workstation is a Mac, you can download the latest version of Kots CLI Darwin binary from https://kots.io/.

Push the Admin Console images to your private registry:

kubectl kots admin-console push-images ./kotsadm.tar.gz [Your private registry host]/arthurai \
  --registry-username [Read-Write Username] \
  --registry-password [Read-Write Password] 

As an option, you can also pre-upload the application images to your private registry before running the installer:

kubectl kots admin-console push-images ./arthur-x.x.x.airgap [Your private registry host]/arthurai \
  --registry-username [Read-Write Username] \
  --registry-password [Read-Write Password] 

Install the Admin Console:

kubectl kots install arthur \
  --port-forward=false \
  --namespace arthur \
  --kotsadm-namespace arthurai \
  --kotsadm-registry [Your private container image repository] \
  --registry-username [Read-Write Username] \
  --registry-password [Read-Write Password]

Create a port forwarding tunnel to Admin Console. Go to http://localhost:8800 to access the Admin Console:

kubectl kots admin-console --namespace arthur

Follow the instructions on the Admin Console to complete your installation by providing the arthur-x.x.x.airgap bundle and necessary configurations.

Monitor the Admin Console dashboard for the application status to become Ready.

.png image

To see the progress of the deployment, monitor the deployment status with kubectl CLI:

kubectl get deployment,statefulset,pod -n <yournamespace>

If anything is showing Pending, it is likely you need to add more/bigger nodes to your cluster.

Configure graphs on Admin Console by clicking on the Configure graphs button and providing your Prometheus endpoint (e.g. http://kube-prometheus-stack-prometheus.monitoring.svc.cluster.local:9090).