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
the SPI type EbsVolumeMapping and kmsKeyId differ by a typo from the Karpenter CRD which is written kmsKeyID
Expected Behavior
correct the typo in the context of Karpenter EC2NodeClass: kmsKeyID
Current Behavior
kmsKeyId
Which output the following error in the kubectl lambda:
Error from server (BadRequest): error when creating "/tmp/manifest.yaml": EC2NodeClass in version "v1beta1" cannot be handled as a EC2NodeClass: strict decoding error: unknown field "spec.blockDeviceMappings[0].ebs.kmsKeyId", unknown field "spec.blockDeviceMappings[1].ebs.kmsKeyId"\n'
Reproduction Steps
.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.148.1 (build 283525d)
EKS Blueprints Version
1.15.1
Node.js Version
v20.11.1
Environment details (OS name and version, etc.)
macos sonoma
Other information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
the SPI type
EbsVolumeMapping
andkmsKeyId
differ by a typo from the Karpenter CRD which is writtenkmsKeyID
Expected Behavior
correct the typo in the context of Karpenter EC2NodeClass:
kmsKeyID
Current Behavior
kmsKeyId
Which output the following error in the kubectl lambda:
Reproduction Steps
.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.148.1 (build 283525d)
EKS Blueprints Version
1.15.1
Node.js Version
v20.11.1
Environment details (OS name and version, etc.)
macos sonoma
Other information
No response
The text was updated successfully, but these errors were encountered: