The Galileo applications run on managed Kubernetes-like environments, but this document will specifically cover the configuration and deployment of an Exoscale Cloud SKS environment.
Configuration | Recommended Value |
---|---|
Nodes in the cluster’s core nodegroup | 5 |
CPU per core node | 4 CPU |
RAM per core node | 16 GiB RAM |
Minimum volume size per node | 400 GiB |
Number of nodes in the cluster’s runners nodegroup | 2 |
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.24 |
Mandatory Field | Description |
---|---|
SKS Cluster Name | The SKS cluster name |
Galileo runner instance pool ID | SKS galileo-runner instance pool ID |
Exoscale API keys | Exoscale EXOSCALE_API_KEY and EXOSCALE_API_SECRET with Object Storage Buckets permissions: - create - get - list |
Exoscale storage host | e.g sos-ch-gva-2.exo.io |
Domain Name | The customer wishes to deploy the cluster under e.g. google.com |
Root subdomain | e.g. “galileo” as in galileo.google.com |
Trusted SSL Certificates (Optional) | By default, Galileo provisions Let’s Encrypt certificates. But if you wish to use your own trusted SSL certificates, you should submit a base64 encoded string of 1. the full certificate chain, and 2. another, separate base64 encoded string of the signing key. |
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…] |