-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Scope CloudFormation Permissions #3948
chore: Scope CloudFormation Permissions #3948
Conversation
✅ Deploy Preview for karpenter-docs-prod canceled.
|
d7f4de4
to
1ff134e
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
1ff134e
to
1f05812
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
1f05812
to
b292a35
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
0df15aa
to
498a4bf
Compare
I wonder if it is too much to ask that once you finish the cloudformation policy updates, if you wouldnt mind also updating the terraform ones? cc @bryantbiggs |
@bryantbiggs There may be some room to align here. There are some cluster-scoped tags that Karpenter already uses by default that might be good to use as part of the default policy rather than asking the user to pass through an IRSA tag that they would also have to pass through to their |
website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml
Outdated
Show resolved
Hide resolved
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.
/karpenter snapshot
Snapshot successfully published to |
e62c0f7
to
d52d192
Compare
website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml
Show resolved
Hide resolved
website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml
Outdated
Show resolved
Hide resolved
website/content/en/preview/getting-started/getting-started-with-karpenter/cloudformation.yaml
Outdated
Show resolved
Hide resolved
ee2e43f
to
4da472f
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
f561954
to
7accfa7
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
7accfa7
to
d4a2316
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
d4a2316
to
1d67741
Compare
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.
/karpenter snapshot
Snapshot successfully published to |
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.
/karpenter snapshot
Snapshot successfully published to |
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.
lgtm
Fixes #
Description
Updates CloudFormation permissions in the "Getting Started Guide" to be scoped to sufficiently restrict the tags that can be used when provisioning nodes with Karpenter. It also enforce tag-based authz on the karpenter controller by default.
Note that the CloudFormation file and the permissions that are provided there-in only serve as a starting point for users. The permissions will most likely have to be extended to some degree for most use-cases.
How was this change tested?
/karpenter snapshot
Does this change impact docs?
Release Note
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.