Description

Exposing the tenancy field in the AwsNodeTemplate API will help allow AWS GovCloud customers and anyone else that requires an extra level of security use Karpenter without compromise.

What problem are you trying to solve?

For AWS customers trying to maintain IL5 compliance, Kubernetes clusters must use dedicated instances. Since Karpenter does not expose the tenancy field of instance configuration in the AwsNodeTemplate spec, it means that NodeTemplates have to be used. This causes a lot of friction when trying to run Karpenter as different userdata fields, and therefore different NodeTemplates have to be made based on the instance type being used.

How important is this feature to you?

Without the ability to set the tenancy field, we cannot take advantage of the dynamic node right-sizing features that Karpenter has built in, and we are forced to restrict everything down to a single instance type. Exposing this API field would allow any AWS GovCloud customers attempting to run an IL5 compliant cluster to use Karpenter to its full potential.

I am interested and willing to work on this issue if it helps to move this issue forward.