Self-Hosted Kubernetes Cluster
Azure AKS
This page details the steps to deploy a Galileo Kubernetes cluster in Microsoft Azure’s AKS service environment.
**
Total time for deployment:** 30-45 minutesRecommended Cluster Configuration
Configuration | Recommended Value |
---|---|
Nodes in the cluster’s core nodegroup | 4 (min) 5 (max) 4 (desired) |
CPU per core node | 4 CPU |
RAM per core node | 16 GiB RAM |
Number of nodes in the cluster’s runners nodegroup | 1 (min) 5 (max) 1 (desired) |
CPU per runner node | 8 CPU |
RAM per runner node | 32 GiB RAM |
Minimum volume size per node | 200 GiB |
Required Kubernetes API version | 1.21 |
Storage class | standard |
Step 1: [Optional] Create a dedicated resource group for Galileo cluster
Step 2: Provision an AKS cluster
Step 3: Add Galileo Runner nodepool
Step 4: Get cluster credentials
Step 5: Apply Galileo manifest
Step 6: Customer DNS Configuration
Galileo has 4 main URLs (shown below). In order to make the URLs accessible across the company, you have to set the following DNS addresses in your DNS provider after the platform is deployed.
Service | URL |
---|---|
API | api.galileo.company.[com|ai|io…] |
Data | data.galileo.company.[com|ai|io…] |
UI | console.galileo.company.[com|ai|io…] |
Grafana | grafana.galileo.company.[com|ai|io…] |
Creating a GPU-enabled Node Group
For specialized tasks that require GPU processing, such as machine learning workloads, Galileo supports the configuration of GPU-enabled node pools.
-
Node Group Creation: Create a
NCas_T4_v3-series
node group with namegalileo-ml
, min_size 1, max_size 5, and labelgalileo-node-type=galileo-ml
-
When this is done, please reach out to Galileo team so that we can update the deployment config for you.
Was this page helpful?