kubespray/contrib/azurerm
MarkusTeufelberger e67f848abc ansible-lint: add spaces around variables [E206] (#4699) 2019-05-02 14:24:21 -07:00
..
group_vars Add the option to create a DNS record for bastion deployed to Azure (#3675) 2018-11-09 11:30:35 +01:00
roles ansible-lint: add spaces around variables [E206] (#4699) 2019-05-02 14:24:21 -07:00
.gitignore Add Azure Resource Manager templates to contrib folder 2016-12-13 15:37:04 +01:00
README.md docs(azure cli): update links 2018-06-07 07:10:33 +02:00
apply-rg.sh fix issues with if condition (#1537) 2017-08-20 13:55:13 +03:00
apply-rg_2.sh update azure contrib to use azure cli 2.0 2017-08-11 20:13:02 +02:00
clear-rg.sh fix issues with if condition (#1537) 2017-08-20 13:55:13 +03:00
clear-rg_2.sh update azure contrib to use azure cli 2.0 2017-08-11 20:13:02 +02:00
generate-inventory.sh fix issues with if condition (#1537) 2017-08-20 13:55:13 +03:00
generate-inventory.yml Add Azure Resource Manager templates to contrib folder 2016-12-13 15:37:04 +01:00
generate-inventory_2.yml update azure contrib to use azure cli 2.0 2017-08-11 20:13:02 +02:00
generate-templates.yml Add Azure Resource Manager templates to contrib folder 2016-12-13 15:37:04 +01:00

README.md

Kubernetes on Azure with Azure Resource Group Templates

Provision the base infrastructure for a Kubernetes cluster by using Azure Resource Group Templates

Status

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).

Requirements

Configuration through group_vars/all

You have to modify at least one variable in group_vars/all, which is the cluster_name variable. It must be globally unique due to some restrictions in Azure. Most other variables should be self explanatory if you have some basic Kubernetes experience.

Bastion host

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.

Generating and applying

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.

Clearing a resource group

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!

Generating an inventory for kubespray

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
$ ansible-playbook -i contrib/azurerm/inventory -u devops --become -e "@inventory/sample/group_vars/all.yml" cluster.yml