You should see “Merged “kubernetes-cluster-name” as current context in /home/yourname/.kube/config”ģ - Inspect this config file. To do the actual connection, I followed the steps here:ġ - In the Azure portal open the cloud cli, or run your local Azure cli.Ģ - Run this, substituting the name of your resource group and cluster az aks get-credentials -resource-group -name Waiting is important here! I’ve got my Gitlab setup into a mess in the past by trying to use connect to my cluster before it was ready. Next, I waited for the cluster to deploy. I did however add ‘Http application routing’ so that Azure would give me an automatic domain name for my cluster, making testing and troubleshooting easier. I chose to leave RBAC disabled as Gitlab is a couple of months away from properly supporting this superior authentication method. I spun up a cluster using the managed ‘Azure Kubernetes Service’ available from the Azure Portal UI. Gitlab isn’t doing anything fancy here, but I’d rather be under their umbrella than banging on the cli on my own so I like the idea of this.įirst you need to setup your cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |