Azure AKS
Importing an Azure AKS engine connects an existing AKS cluster to AIchor without transferring ownership. AIchor schedules workloads on the cluster using the provided Azure credentials, while infrastructure management remains with the cluster administrator.
Prerequisites
-
The AKS cluster must already exist and be accessible.
-
The Azure subscription ID, tenant ID, and resource group name must be known.
-
The Kubernetes API server endpoint is required. Run the following command to retrieve it:
kubectl cluster-info
and look for the Kubernetes control plane endpoint.
- The IPv4 address of the Azure load balancer must be available.
Steps
- In the AIchor UI, open Engines and click Add Engine.
- Select In The Cloud, then Azure, then AKS.
- Select Import Existing Engine.
- Fill in the form fields described below and submit.
Form fields
| Field | Required | Description |
|---|---|---|
| Engine Name | Yes | Name of the engine in AIchor. Lowercase alphanumeric characters and hyphens. Must start with a letter. |
| AKS Cluster Name | Yes | Name of the existing AKS cluster to import. |
| Azure Subscription | Yes | Azure subscription ID containing the cluster. |
| Azure Tenant ID | Yes | Azure Active Directory tenant ID. |
| Azure Resource Group Name | Yes | Resource group containing the cluster. |
| Azure Load Balancer IP | Yes | IPv4 address of the Azure load balancer. |
| API Hostname | Yes | Kubernetes API server endpoint. Found in ~/.kube/config under the cluster's server field. |
| MS Azure Region | Yes | Region where the cluster runs. |
| Ecosystem | No | Tag passed to infrastructure-as-code tooling. Required only for specific organisations on InstaDeep recommendation. |
Certificates
| Field | Required | Description |
|---|---|---|
| CA Data | No | Certificate Authority certificate in PEM format. |