-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Karpenter & External residing CMK #2052
Comments
There is one thing that I missed out on, I was able it work by creating a 'new' Grant in the account that is consuming the KMS for the autoscaling role. Support engineers indicate that this should be a one time activity for when a new autoscaling role get created. |
The updated iam.tf will have the following lines of permission to add the CreateGrant action.
The awscli cmd :
However what bugs me is the fact that the CT logs indicate the my full admin role as 'username' making the 'CreateGrant' API call. When it should be the autoscaling group role making the trigger. |
This issue has been automatically marked as stale because it has been open 30 days |
Issue closed due to inactivity. |
Please describe your question here
A quite simple problem statement has bugged me lately,
Karpenter is unable to provision node groups with AMI that have the EBS volume encrypted with a CMK in an external account.
As the node get created, however instantaneous get terminated due error message : [Client.InvalidKMSKey.InvalidState]
I followed this AWS Document, that'll help me add permissions to the karpenter-worker-nodes roles. however I still get the same error.
The role file looks like this ::
resource "aws_iam_role_policy_attachment" "karpenter_controller_attach" {
depends_on = [aws_iam_policy.karpenter_controller, aws_iam_role.karpenter_controller]
role = aws_iam_role.karpenter_controller.name
policy_arn = aws_iam_policy.karpenter_controller.arn
}
`
Few Qs,
I currently use following seq to provision my nodegroup
A grant is been created on the Key owner account & cross-account-kms on the consumer account
I was curious to know, if there are any other piece of infra need to integrated so that Karpenter can create nodegroups from AMIs that have encrypted snapshot with an external residing CMK.
The text was updated successfully, but these errors were encountered: