Skip to content

Commit

Permalink
CA - AWS - Update OIDC example docs
Browse files Browse the repository at this point in the history
  • Loading branch information
gjtempleton committed Feb 16, 2022
1 parent bffaef5 commit 321298a
Showing 1 changed file with 13 additions and 5 deletions.
18 changes: 13 additions & 5 deletions cluster-autoscaler/cloudprovider/aws/CA_with_AWS_IAM_OIDC.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,9 +53,11 @@ D) Set up [Cluster Autoscaler Auto-Discovery] using the [tutorial] .

Note: The keys for the tags that you entered don't have values. Cluster Autoscaler ignores any value set for the keys.

- Create an IAM Policy for cluster autoscaler and to enable AutoDiscovery.
__NOTE:__ Please see [the README](README.md#IAM-Policy) for more information on best practices with this IAM role.

```sh
- Create an IAM Policy for cluster autoscaler and to enable AutoDiscovery as well as discovery of instance types.

```json
{
"Version": "2012-10-17",
"Statement": [
Expand All @@ -66,17 +68,23 @@ Note: The keys for the tags that you entered don't have values. Cluster Autoscal
"autoscaling:DescribeAutoScalingInstances",
"autoscaling:DescribeLaunchConfigurations",
"autoscaling:DescribeTags",
"ec2:DescribeInstanceTypes",
"ec2:DescribeLaunchTemplateVersions"
],
"Resource": ["*"]
},
{
"Effect": "Allow",
"Action": [
"autoscaling:SetDesiredCapacity",
"autoscaling:TerminateInstanceInAutoScalingGroup"
],
"Resource": "*"
"Resource": ["*"]
}
]
}
```

NOTE: ``` autoscaling:DescribeTags ``` is very important if you are making use of the AutoDiscovery feature of the Cluster AutoScaler.

- Attach the above created policy to the *instance role* that's attached to your Amazon EKS worker nodes.
- Download a deployment example file provided by the Cluster Autoscaler project on GitHub, run the following command:

Expand Down

0 comments on commit 321298a

Please sign in to comment.