kubernetes
/
autoscaler
mirror of https://github.com/kubernetes/autoscaler.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
autoscaler/cluster-autoscaler/cloudprovider/azure
History
Pengfei Ni d7d8601011 Update deployment guides 2017-12-29 10:04:44 +08:00
..
README.md Update deployment guides 2017-12-29 10:04:44 +08:00
azure_agent_pool.go Add support for acs-engine managed agent pools 2017-12-29 10:04:09 +08:00
azure_cloud_provider.go Add support for acs-engine managed agent pools 2017-12-29 10:04:09 +08:00
azure_cloud_provider_test.go Add unit tests 2017-12-29 10:04:09 +08:00
azure_fakes.go Add mock clients 2017-12-29 10:04:09 +08:00
azure_manager.go Add support for acs-engine managed agent pools 2017-12-29 10:04:09 +08:00
azure_scale_set.go Move ScaleSet to a separate file 2017-12-29 10:04:09 +08:00
azure_scale_set_test.go Add unit tests 2017-12-29 10:04:09 +08:00
azure_util.go Add support for acs-engine managed agent pools 2017-12-29 10:04:09 +08:00
azure_util_test.go Add unit tests 2017-12-29 10:04:09 +08:00
cluster-autoscaler-standard-master.yaml Update deployment guides 2017-12-29 10:04:44 +08:00
cluster-autoscaler-standard.yaml Update deployment guides 2017-12-29 10:04:44 +08:00
cluster-autoscaler-vmss-master.yaml Update deployment guides 2017-12-29 10:04:44 +08:00
cluster-autoscaler-vmss.yaml Update deployment guides 2017-12-29 10:04:44 +08:00

README.md

Cluster Autoscaler on Azure

The cluster autoscaler on Azure scales worker nodes within any specified autoscaling group. It will run as a Kubernetes deployment in your cluster. This README will go over some of the necessary steps required to get the cluster autoscaler up and running.

Kubernetes Version

Cluster autoscaler support two VM types with Azure cloud provider:

  • vmss: For kubernetes cluster running on VMSS instances. Azure cloud provider's vmType parameter must be configured as 'vmss'. It requires Kubernetes with Azure VMSS support (kubernetes#43287), which is planed in Kubernetes v1.10.
  • standard: For kubernetes cluster running on VMAS instances. Azure cloud provider's vmType parameter must be configured as 'standard'. It only supports Kubernetes cluster deployed via acs-engine.

Permissions

Get azure credentials by running the following command

# replace <subscription-id> with yours.
az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/<subscription-id>" --output json

Deployment manifests

VMSS deployment

Pre-requirements:

  • Get credentials from above permissions step.
  • Get the scale set name which is used for nodes scaling.
  • Encode each data with base64.

Fill the values of cluster-autoscaler-azure secret in cluster-autoscaler-vmss.yaml, including

  • ClientID: <base64-encoded-client-id>
  • ClientSecret: <base64-encoded-client-secret>
  • ResourceGroup: <base64-encoded-resource-group>
  • SubscriptionID: <base64-encode-subscription-id>
  • TenantID: <base64-encoded-tenant-id>
  • NodeGroup: <base64-encoded-scale-set-name>

Note that all data should be encoded with base64.

Then deploy cluster-autoscaler by running

kubectl create -f cluster-autoscaler-vmss.yaml

To run a CA pod in master node - CA deployment should tolerate the master taint and nodeSelector should be used to schedule the pods in master node.

kubectl create -f cluster-autoscaler-vmss-master.yaml

Standard deployment

Pre-requirements:

  • Get credentials from above permissions step.
  • Get the required paramters from acs-engine deployments (usually under directory _output/<master-dns-prefix> after running acs-engine deploy command)
    • Get APIServerPrivateKey, CAPrivateKey, ClientPrivateKey and KubeConfigPrivateKey from azuredeploy.parameters.json
    • If windows nodes are included, also get WindowsAdminPassword from acs-engine deployment manifests
    • Get the initial Azure deployment name from azure portal. If you have multiple deployments (e.g. have run acs-engine scale command), make sure to get the first one
    • Get a node pool name for nodes scaling from acs-engine deployment manifests
  • Encode each data with base64.

Fill the values of cluster-autoscaler-azure secret in cluster-autoscaler-standard.yaml, including

  • ClientID: <base64-encoded-client-id>
  • ClientSecret: <base64-encoded-client-secret>
  • ResourceGroup: <base64-encoded-resource-group>
  • SubscriptionID: <base64-encode-subscription-id>
  • TenantID: <base64-encoded-tenant-id>
  • NodeGroup: <base64-encoded-node-pool-name>
  • Deployment: <base64-encoded-azure-initial-deploy-name>
  • APIServerPrivateKey: <base64-encoded-apiserver-private-key>
  • CAPrivateKey: <base64-encoded-ca-private-key>
  • ClientPrivateKey: <base64-encoded-client-private-key>
  • KubeConfigPrivateKey: <base64-encoded-kubeconfig-private-key>
  • WindowsAdminPassword: <base64-encoded-windows-admin-password>

Note that all data should be encoded with base64.

Then deploy cluster-autoscaler by running

kubectl create -f cluster-autoscaler-standard.yaml

To run a CA pod in master node - CA deployment should tolerate the master taint and nodeSelector should be used to schedule the pods in master node.

kubectl create -f cluster-autoscaler-standard-master.yaml