Skip to content

Commit

Permalink
Add ReplaceRoute to the capa-controller-policy
Browse files Browse the repository at this point in the history
In certain circumstances, CAPA tries to replace routes but gets blocked
by IAM policy. This causes nodes to spin up in a `not-ready` state

changelog
  • Loading branch information
mproffitt committed Aug 2, 2024
1 parent 14b0a1a commit 0800a25
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 0 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

- Add `ec2:ReplaceRoute` permissions to the CAPA controller role

### Added

- For cluster cleanup purposes, add the permissions `s3:GetBucketTagging` and `s3:ListAllMyBuckets` in order to scan for buckets owned by a management/workload cluster. Those buckets may not have a fixed name pattern (e.g. include AWS region or other dynamic string) and therefore searching by "owned" tag allows us to find and delete all such resources.
Expand Down
1 change: 1 addition & 0 deletions capa-controller-role/capa-controller-policy.json
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@
"ec2:ModifyNetworkInterfaceAttribute",
"ec2:ModifySubnetAttribute",
"ec2:ReleaseAddress",
"ec2:ReplaceRoute",
"ec2:RevokeSecurityGroupIngress",
"ec2:RevokeSecurityGroupEgress",
"ec2:RunInstances",
Expand Down

0 comments on commit 0800a25

Please sign in to comment.