Update link to deprecated repository (#5965 )

https://github.com/colemickens/azure-kubernetes-status is deprecated
and will be removed soon as the README.
So this updates the link to the repository for a new one.

2020-04-17 04:07:07 -07:00

3.9 KiB

Raw Blame History

Azure

To deploy Kubernetes on Azure uncomment the cloud_provider option in group_vars/all.yml and set it to 'azure'.

All your instances are required to run in a resource group and a routing table has to be attached to the subnet your instances are in.

Not all features are supported yet though, for a list of the current status have a look here

Parameters

Before creating the instances you must first set the azure_ variables in the group_vars/all.yml file.

All of the values can be retrieved using the azure cli tool which can be downloaded here: https://docs.microsoft.com/en-gb/azure/xplat-cli-install After installation you have to run azure login to get access to your account.

azure_tenant_id + azure_subscription_id

run azure account show to retrieve your subscription id and tenant id: azure_tenant_id -> Tenant ID field azure_subscription_id -> ID field

azure_location

The region your instances are located, can be something like westeurope or westcentralus. A full list of region names can be retrieved via azure location list

azure_resource_group

The name of the resource group your instances are in, can be retrieved via azure group list

azure_vmtype

The type of the vm. Supported values are standard or vmss. If vm is type of Virtal Machines then value is standard. If vm is part of Virtaul Machine Scale Sets then value is vmss

azure_vnet_name

The name of the virtual network your instances are in, can be retrieved via azure network vnet list

azure_subnet_name

The name of the subnet your instances are in, can be retrieved via azure network vnet subnet list --resource-group RESOURCE_GROUP --vnet-name VNET_NAME

azure_security_group_name

The name of the network security group your instances are in, can be retrieved via azure network nsg list

azure_aad_client_id + azure_aad_client_secret

These will have to be generated first:

Create an Azure AD Application with: azure ad app create --display-name kubernetes --identifier-uris http://kubernetes --homepage http://example.com --password CLIENT_SECRET display name, identifier-uri, homepage and the password can be chosen Note the AppId in the output.
Create Service principal for the application with: azure ad sp create --id AppId This is the AppId from the last command
Create the role assignment with: azure role assignment create --role "Owner" --assignee http://kubernetes --subscription SUBSCRIPTION_ID

azure_aad_client_id must be set to the AppId, azure_aad_client_secret is your chosen secret.

azure_loadbalancer_sku

Sku of Load Balancer and Public IP. Candidate values are: basic and standard.

azure_exclude_master_from_standard_lb

azure_exclude_master_from_standard_lb excludes master nodes from standard load balancer.

azure_disable_outbound_snat

azure_disable_outbound_snat disables the outbound SNAT for public load balancer rules. It should only be set when azure_exclude_master_from_standard_lb is standard.

azure_primary_availability_set_name

(Optional) The name of the availability set that should be used as the load balancer backend .If this is set, the Azure cloudprovider will only add nodes from that availability set to the load balancer backend pool. If this is not set, and multiple agent pools (availability sets) are used, then the cloudprovider will try to add all nodes to a single backend pool which is forbidden. In other words, if you use multiple agent pools (availability sets), you MUST set this field.

azure_use_instance_metadata

Use instance metadata service where possible

Provisioning Azure with Resource Group Templates

You'll find Resource Group Templates and scripts to provision the required infrastructure to Azure in contrib/azurerm

3.9 KiB Raw Blame History