Skip to content

Commit bcb7bc6

Browse files
committed
docs: Change node role policy ReadOnly -> PullOnly (support ECR pull-through cache)
1 parent b83ea6b commit bcb7bc6

File tree

22 files changed

+32
-40
lines changed

22 files changed

+32
-40
lines changed

Diff for: test/cloudformation/iam_cloudformation.yaml

+4-12
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ Resources:
270270
# CI task. This includes the cluster ServiceRoles that are generated by EKSCTL and all roles generated with IRSA to interface from the
271271
# cluster into AWS services through IAM.
272272
# The policies that are captured inside the GithubActionsPermissionsBoundary include:
273-
# - AmazonEC2ContainerRegistryReadOnly
273+
# - AmazonEC2ContainerRegistryPullOnly
274274
# - AmazonEKSWorkerNodePolicy
275275
# - AmazonSSMManagedInstanceCore
276276
# - AmazonEBSCSIDriverPolicy
@@ -288,19 +288,11 @@ Resources:
288288
- Effect: Allow
289289
Action:
290290
- ec2:*
291-
# Read-Only Permissions to pull ECR images needed by the NodeInstanceRole
291+
# Permissions to pull ECR images needed by the NodeInstanceRole
292292
- ecr:GetAuthorizationToken
293-
- ecr:BatchCheckLayerAvailability
294-
- ecr:GetDownloadUrlForLayer
295-
- ecr:GetRepositoryPolicy
296-
- ecr:DescribeRepositories
297-
- ecr:ListImages
298-
- ecr:DescribeImages
299293
- ecr:BatchGetImage
300-
- ecr:GetLifecyclePolicy
301-
- ecr:GetLifecyclePolicyPreview
302-
- ecr:ListTagsForResource
303-
- ecr:DescribeImageScanFindings
294+
- ecr:GetDownloadUrlForLayer
295+
- ecr:BatchImportUpstreamImage
304296
# EKS ServiceRole permissions needed for AutoScalingGroups
305297
- autoscaling:DescribeAutoScalingGroups
306298
- autoscaling:UpdateAutoScalingGroup

Diff for: website/content/en/docs/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/docs/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy"
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
8+
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore"

Diff for: website/content/en/docs/reference/cloudformation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ KarpenterNodeRole:
6666
ManagedPolicyArns:
6767
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
6868
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
69-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
69+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
7070
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
7171
```
7272
7373
The role created here includes several AWS managed policies, which are designed to provide permissions for specific uses needed by the nodes to work with EC2 and other AWS resources. These include:
7474
7575
* [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html): Provides the permissions that the Amazon VPC CNI Plugin needs to configure EKS worker nodes.
7676
* [AmazonEKSWorkerNodePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSWorkerNodePolicy.html): Lets Amazon EKS worker nodes connect to EKS Clusters.
77-
* [AmazonEC2ContainerRegistryReadOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryReadOnly.html): Allows read-only access to repositories in the Amazon EC2 Container Registry.
77+
* [AmazonEC2ContainerRegistryPullOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryPullOnly.html): Allows pulling images from repositories in the Amazon EC2 Container Registry.
7878
* [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html): Adds AWS Systems Manager service core functions for Amazon EC2.
7979
8080
If you were to use a node role from an existing cluster, you could skip this provisioning step and pass this node role to any EC2NodeClasses that you create. Additionally, you would ensure that the [Controller Policy]({{< relref "#controllerpolicy" >}}) has `iam:PassRole` permission to the role attached to the generated instance profiles.

Diff for: website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/preview/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy"
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
8+
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore"

Diff for: website/content/en/preview/reference/cloudformation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ KarpenterNodeRole:
6666
ManagedPolicyArns:
6767
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
6868
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
69-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
69+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
7070
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
7171
```
7272
7373
The role created here includes several AWS managed policies, which are designed to provide permissions for specific uses needed by the nodes to work with EC2 and other AWS resources. These include:
7474
7575
* [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html): Provides the permissions that the Amazon VPC CNI Plugin needs to configure EKS worker nodes.
7676
* [AmazonEKSWorkerNodePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSWorkerNodePolicy.html): Lets Amazon EKS worker nodes connect to EKS Clusters.
77-
* [AmazonEC2ContainerRegistryReadOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryReadOnly.html): Allows read-only access to repositories in the Amazon EC2 Container Registry.
77+
* [AmazonEC2ContainerRegistryPullOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryPullOnly.html): Allows pulling images from repositories in the Amazon EC2 Container Registry.
7878
* [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html): Adds AWS Systems Manager service core functions for Amazon EC2.
7979
8080
If you were to use a node role from an existing cluster, you could skip this provisioning step and pass this node role to any EC2NodeClasses that you create. Additionally, you would ensure that the [Controller Policy]({{< relref "#controllerpolicy" >}}) has `iam:PassRole` permission to the role attached to the generated instance profiles.

Diff for: website/content/en/v0.32/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/v0.32/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly
8+
--policy-arn arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore

Diff for: website/content/en/v0.32/reference/cloudformation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ KarpenterNodeRole:
6666
ManagedPolicyArns:
6767
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
6868
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
69-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
69+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
7070
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
7171
```
7272
7373
The role created here includes several AWS managed policies, which are designed to provide permissions for specific uses needed by the nodes to work with EC2 and other AWS resources. These include:
7474
7575
* [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html): Provides the permissions that the Amazon VPC CNI Plugin needs to configure EKS worker nodes.
7676
* [AmazonEKSWorkerNodePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSWorkerNodePolicy.html): Lets Amazon EKS worker nodes connect to EKS Clusters.
77-
* [AmazonEC2ContainerRegistryReadOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryReadOnly.html): Allows read-only access to repositories in the Amazon EC2 Container Registry.
77+
* [AmazonEC2ContainerRegistryPullOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryPullOnly.html): Allows pulling images from repositories in the Amazon EC2 Container Registry.
7878
* [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html): Adds AWS Systems Manager service core functions for Amazon EC2.
7979
8080
If you were to use a node role from an existing cluster, you could skip this provisioning step and pass this node role to any EC2NodeClasses that you create. Additionally, you would ensure that the [Controller Policy]({{< relref "#controllerpolicy" >}}) has `iam:PassRole` permission to the role attached to the generated instance profiles.

Diff for: website/content/en/v1.0/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/v1.0/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy"
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
8+
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore"

Diff for: website/content/en/v1.0/reference/cloudformation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ KarpenterNodeRole:
6666
ManagedPolicyArns:
6767
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
6868
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
69-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
69+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
7070
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
7171
```
7272
7373
The role created here includes several AWS managed policies, which are designed to provide permissions for specific uses needed by the nodes to work with EC2 and other AWS resources. These include:
7474
7575
* [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html): Provides the permissions that the Amazon VPC CNI Plugin needs to configure EKS worker nodes.
7676
* [AmazonEKSWorkerNodePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSWorkerNodePolicy.html): Lets Amazon EKS worker nodes connect to EKS Clusters.
77-
* [AmazonEC2ContainerRegistryReadOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryReadOnly.html): Allows read-only access to repositories in the Amazon EC2 Container Registry.
77+
* [AmazonEC2ContainerRegistryPullOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryPullOnly.html): Allows pulling images from repositories in the Amazon EC2 Container Registry.
7878
* [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html): Adds AWS Systems Manager service core functions for Amazon EC2.
7979
8080
If you were to use a node role from an existing cluster, you could skip this provisioning step and pass this node role to any EC2NodeClasses that you create. Additionally, you would ensure that the [Controller Policy]({{< relref "#controllerpolicy" >}}) has `iam:PassRole` permission to the role attached to the generated instance profiles.

Diff for: website/content/en/v1.1/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/v1.1/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy"
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
8+
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore"

Diff for: website/content/en/v1.1/reference/cloudformation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ KarpenterNodeRole:
6666
ManagedPolicyArns:
6767
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
6868
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
69-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
69+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
7070
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
7171
```
7272
7373
The role created here includes several AWS managed policies, which are designed to provide permissions for specific uses needed by the nodes to work with EC2 and other AWS resources. These include:
7474
7575
* [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html): Provides the permissions that the Amazon VPC CNI Plugin needs to configure EKS worker nodes.
7676
* [AmazonEKSWorkerNodePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKSWorkerNodePolicy.html): Lets Amazon EKS worker nodes connect to EKS Clusters.
77-
* [AmazonEC2ContainerRegistryReadOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryReadOnly.html): Allows read-only access to repositories in the Amazon EC2 Container Registry.
77+
* [AmazonEC2ContainerRegistryPullOnly](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEC2ContainerRegistryPullOnly.html): Allows pulling images from repositories in the Amazon EC2 Container Registry.
7878
* [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html): Adds AWS Systems Manager service core functions for Amazon EC2.
7979
8080
If you were to use a node role from an existing cluster, you could skip this provisioning step and pass this node role to any EC2NodeClasses that you create. Additionally, you would ensure that the [Controller Policy]({{< relref "#controllerpolicy" >}}) has `iam:PassRole` permission to the role attached to the generated instance profiles.

Diff for: website/content/en/v1.2/getting-started/getting-started-with-karpenter/cloudformation.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Resources:
2222
ManagedPolicyArns:
2323
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKS_CNI_Policy"
2424
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEKSWorkerNodePolicy"
25-
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
25+
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
2626
- !Sub "arn:${AWS::Partition}:iam::aws:policy/AmazonSSMManagedInstanceCore"
2727
KarpenterControllerPolicy:
2828
Type: AWS::IAM::ManagedPolicy

Diff for: website/content/en/v1.2/getting-started/migrating-from-cas/scripts/step03-node-policies.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
55
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEKS_CNI_Policy"
66

77
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
8-
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
8+
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly"
99

1010
aws iam attach-role-policy --role-name "KarpenterNodeRole-${CLUSTER_NAME}" \
1111
--policy-arn "arn:${AWS_PARTITION}:iam::aws:policy/AmazonSSMManagedInstanceCore"

0 commit comments

Comments
 (0)