To deploy Kubernetes on Azure uncomment the cloud_provider
option in group_vars/all/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
Before creating the instances you must first set the azure_
variables in the group_vars/all/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 az login
to get access to your account.
Azure Stack has different API endpoints, depending on the Azure Stack deployment. These need to be provided to the Azure SDK.
Possible values are: AzureChinaCloud
, AzureGermanCloud
, AzurePublicCloud
and AzureUSGovernmentCloud
.
The full list of existing settings for the AzureChinaCloud, AzureGermanCloud, AzurePublicCloud and AzureUSGovernmentCloud
is available in the source code here
run az account show
to retrieve your subscription id and tenant id:
azure_tenant_id
-> Tenant ID field
azure_subscription_id
-> ID field
The region your instances are located, can be something like westeurope
or westcentralus
. A full list of region names can be retrieved via az account list-locations
The name of the resource group your instances are in, can be retrieved via az group list
The type of the vm. Supported values are standard
or vmss
. If vm is type of Virtual Machines
then value is standard
. If vm is part of Virtual Machine Scale Sets
then value is vmss
The name of the virtual network your instances are in, can be retrieved via az network vnet list
The name of the subnet your instances are in, can be retrieved via az network vnet subnet list --resource-group RESOURCE_GROUP --vnet-name VNET_NAME
The name of the network security group your instances are in, can be retrieved via az network nsg list
These will have to be generated first:
az 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.az ad sp create --id AppId
This is the AppId from the last commandaz 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.
Sku of Load Balancer and Public IP. Candidate values are: basic and standard.
azure_exclude_master_from_standard_lb excludes master nodes from standard
load balancer.
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
.
(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.
Use instance metadata service where possible
You'll find Resource Group Templates and scripts to provision the required infrastructure to Azure in contrib/azurerm
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。