This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
AWS Cluster Autoscaler README #1552
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,79 @@ | ||
| # Cluster Autoscaler on AWS | ||
| The cluster autoscaler on AWS scales worker nodes within an autoscaling group. It will run as a `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 must run on v1.3.0 or greater. | ||
|
|
||
| ## Permissions | ||
| The worker running the cluster autoscaler will need access to certain resources and actions: | ||
| ```json | ||
| { | ||
| "Version": "2012-10-17", | ||
| "Statement": [ | ||
| { | ||
| "Effect": "Allow", | ||
| "Action": [ | ||
| "autoscaling:DescribeAutoScalingGroups", | ||
| "autoscaling:DescribeAutoScalingInstances", | ||
| "autoscaling:SetDesiredCapacity", | ||
| "autoscaling:TerminateInstanceInAutoScalingGroup" | ||
| ], | ||
| "Resource": "*" | ||
| } | ||
| ] | ||
| } | ||
| ``` | ||
| Unfortunately AWS does not support ARNs for autoscaling groups yet so you must use "*" as the resource. More information [here](http://docs.aws.amazon.com/autoscaling/latest/userguide/IAM.html#UsingWithAutoScaling_Actions). | ||
|
|
||
| ## Deployment Specification | ||
| Your deployment configuration should look something like this: | ||
| ```yaml | ||
| --- | ||
| apiVersion: extensions/v1beta1 | ||
| kind: Deployment | ||
| metadata: | ||
| name: cluster-autoscaler | ||
| labels: | ||
| app: cluster-autoscaler | ||
| spec: | ||
| replicas: 1 | ||
| selector: | ||
| matchLabels: | ||
| app: cluster-autoscaler | ||
| template: | ||
| metadata: | ||
| labels: | ||
| app: cluster-autoscaler | ||
| spec: | ||
| containers: | ||
| - image: {{ YOUR IMAGE HERE }} | ||
| name: cluster-autoscaler | ||
| resources: | ||
| limits: | ||
| cpu: 100m | ||
| memory: 300Mi | ||
| requests: | ||
| cpu: 100m | ||
| memory: 300Mi | ||
| command: | ||
| - ./cluster-autoscaler | ||
| - -v=4 | ||
| - --cloud-provider=aws | ||
| - --skip-nodes-with-local-storage=false | ||
| - --nodes={{ ASG MIN e.g. 1 }}:{{ASG MAX e.g. 5}}:{{ASG NAME e.g. k8s-worker-asg}} | ||
| env: | ||
| - name: AWS_REGION | ||
| value: us-east-1 | ||
| volumeMounts: | ||
| - name: ssl-certs | ||
| mountPath: /etc/ssl/certs/ca-certificates.crt | ||
| readOnly: true | ||
| imagePullPolicy: "Always" | ||
| volumes: | ||
| - name: ssl-certs | ||
| hostPath: | ||
| path: "/etc/ssl/certs/ca-certificates.crt" | ||
| ``` | ||
| Note: | ||
| - The `/etc/ssl/certs/ca-certificates.crt` should exist by default on your ec2 instance. | ||
| - The autoscaling group should span 1 availability zone for the cluster autoscaler to work. If you want to distribute workloads evenly across zones, set up multiple ASGs, with a cluster autoscaler for each ASG. At the time of writing this, cluster autoscaler is unaware of availability zones and although autoscaling groups can contain instances in multiple availability zones when configured so, the cluster autoscaler can't reliably add nodes to desired zones. That's because AWS AutoScaling determines which zone to add nodes which is out of the control of the cluster autoscaler. For more information, see https://github.com/kubernetes/contrib/pull/1552#discussion_r75533090. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the GCE example in this repo had this:
I'm not sure if this difference would cause issues in other setups?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iterion, where is this example? I can't find it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pbitty think he was referring to https://github.com/kubernetes/contrib/blob/master/cluster-autoscaler/deploy/ca-controller.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iterion there's a lot of other certs in that directory in most ec2 instances, not sure if we want all of them mounted so for aws it could be problematic?