Provision the base infrastructure for a Kubernetes cluster by using Azure Resource Group Templates
This will provision the base infrastructure (vnet, vms, nics, ips, ...) needed for Kubernetes in Azure into the specified Resource Group. It will not install Kubernetes itself, this has to be done in a later step by yourself (using kubespray of course).
- Install azure-cli
- Login with azure-cli
- Dedicated Resource Group created in the Azure Portal or through azure-cli
You have to modify at least two variables in group_vars/all. The one is the cluster_name variable, it must be globally unique due to some restrictions in Azure. The other one is the ssh_public_keys variable, it must be your ssh public key to access your azure virtual machines. Most other variables should be self explanatory if you have some basic Kubernetes experience.
You can enable the use of a Bastion Host by changing use_bastion in group_vars/all to true. The generated templates will then include an additional bastion VM which can then be used to connect to the masters and nodes. The option also removes all public IPs from all other VMs.
To generate and apply the templates, call:
$ ./apply-rg.sh <resource_group_name>If you change something in the configuration (e.g. number of nodes) later, you can call this again and Azure will take care about creating/modifying whatever is needed.
If you need to delete all resources from a resource group, simply call:
$ ./clear-rg.sh <resource_group_name>WARNING this really deletes everything from your resource group, including everything that was later created by you!
After you have applied the templates, you can generate an inventory with this call:
$ ./generate-inventory.sh <resource_group_name>It will create the file ./inventory which can then be used with kubespray, e.g.:
$ cd kubespray-root-dir
$ sudo pip3 install -r requirements.txt
$ ansible-playbook -i contrib/azurerm/inventory -u devops --become -e "@inventory/sample/group_vars/all/all.yml" cluster.yml