- Creating the AKS cluster
- External Access to GitLab
- Next Steps
For a fully functional GitLab instance, you need a few resources before deploying the GitLab chart to Azure Kubernetes Service (AKS).
To get started easier, a script is provided to automate the cluster creation. Alternatively, a cluster can be created manually as well.
A bootstrap script has been created to automate much of the setup process for users on Azure.
It reads an argument of
creds, with additional optional parameters
from environment variables, or command line arguments:
To create the cluster:
- Create a new Resource Group (optional).
- Create a new AKS cluster.
- Create a new Public IP (optional).
To clean up the created AKS resources:
- Delete the specified Resource Group (optional).
- Delete the AKS cluster.
- Delete the Resource Group created by the cluster.
downargument will send the command to delete all resources and finish instantly. The actual deletion can take several minutes to complete.
kubectlto the cluster:
The table below describes all available variables.
|Name of the resource group to use.||All|
|Name of the cluster to use.||All|
|Region to install the cluster in.|
|Version of Kubernetes to use for creating the cluster.||Latest|
|Number of nodes to use.|
|Type of nodes to use.|
|Name of the public IP to create.|
|Create a new resource group to hold all created resources.|
|Create a public IP to use with the new cluster.|
|Delete the resource group when using the down command.|
|Kubernetes configuration file to update. Use |
A cluster with 8vCPU and 30GB of RAM is recommended.
For the most up to date instructions, follow Microsoft’s AKS walkthrough.
An external IP is required so that your cluster can be reachable. For the most up to date instructions, follow Microsoft’s Create a static IP address guide.
Continue with the installation of the chart once you have the cluster up and running, and the static IP and DNS entry ready.