You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But also - in the meantime - I believe this provides a way to workaround this limitation using transforms:
import*asawsfrom"@pulumi/aws";import*aseksfrom"@pulumi/eks";constcluster=neweks.Cluster("cluster",{});constkey=newaws.kms.Key("key");constnodeGroup=neweks.NodeGroupV2("workers",{cluster: cluster,nodeRootVolumeEncrypted: true,},{transforms: [args=>{if(args.type=="aws:ec2/launchTemplate:LaunchTemplate"){// The `eks.NodeGroupV2` component will create a `LaunchTemplate` with `blockDeviceMappings`,// we just need to fill in the `kmsKeyId` as well.constprops=args.props;for(constbdmofprops.blockDeviceMappings){bdm.ebs.kmsKeyId=key.id;}return{ props,opts: args.opts};}return;}]});
Note: The new transforms resources option is recent, and documentation for it is in the works now. It replaces the previous transformations option, and in particular enables the core feature to work with components like @pulumi/eks which are implemented using Component Packages authored in different languages than the user program.
Hello!
Issue details
In this PR we added the ability to encrypt block devices for nodes, but you can't set your own KMS key to do this
Affected area/feature
The text was updated successfully, but these errors were encountered: