/kind feature
Describe the solution you'd like
AWSLaunchTemplate does not expose EnclaveOptions, which means CAPA users
cannot enable AWS Nitro Enclaves on managed machine pool nodes. The field is
available in the EC2 launch template API (LaunchTemplateEnclaveOptionsRequest)
but has never been wired into the CAPA types or launch template builder.
The fix appears straightforward: add an EnclaveOptions struct to api/v1beta2
and a corresponding field on AWSLaunchTemplate, then map it through
createLaunchTemplateData(), SDKToLaunchTemplate(), and
LaunchTemplateNeedsUpdate() — following the same pattern as
InstanceMetadataOptions.
This was called out as a motivating example in the original launch template
proposal (docs/proposal/20211210-launch-templates-managedmachinepools.md).
Anything else you would like to add:
I can work on a PR with the implementation, tests, and documentation.
Environment:
- Cluster-api-provider-aws version: main
- Kubernetes version: N/A
- OS: N/A
/kind feature
Describe the solution you'd like
AWSLaunchTemplatedoes not exposeEnclaveOptions, which means CAPA userscannot enable AWS Nitro Enclaves on managed machine pool nodes. The field is
available in the EC2 launch template API (
LaunchTemplateEnclaveOptionsRequest)but has never been wired into the CAPA types or launch template builder.
The fix appears straightforward: add an
EnclaveOptionsstruct toapi/v1beta2and a corresponding field on
AWSLaunchTemplate, then map it throughcreateLaunchTemplateData(),SDKToLaunchTemplate(), andLaunchTemplateNeedsUpdate()— following the same pattern asInstanceMetadataOptions.This was called out as a motivating example in the original launch template
proposal (docs/proposal/20211210-launch-templates-managedmachinepools.md).
Anything else you would like to add:
I can work on a PR with the implementation, tests, and documentation.
Environment: