Karpenter does not honour custom logging parameters in BottlerocketOS v1.39.1

[ThiyaguE]

Description

Observed Behavior:
BottlerocketOS v1.39.1 support new Kubelet parameters like "containerLogMaxWorkers" & "containerLogMonitorInterval"; If I add these parameters in ec2nodeclass/user-data via [settings.kubernetes] fields, Karpenter is not passing custom values to bottlerocket ec2 instance creation.

Expected Behavior:
Karpenter pass custom values correctly

Reproduction Steps (Please include YAML):
add these parameters in ec2nodeclass/user-data under [settings.kubernetes] field, let karpenter to create instance using this nodeclass and check configs at bottlerocket node.

Versions: Bottlerocket v1.39.1, Karpenter 1.3.1

• Chart Version:
• Kubernetes Version (kubectl version): v1.32.5-eks-5d4a308

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[k8s-ci-robot]

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[engedaam]

Can you move this to AWS provider? Since this is a cloud provider specific functionality

[jonathan-innis]

Closing this since this needs to be opened in the provider repo rather than the upstream repo
/close

[k8s-ci-robot]

@jonathan-innis: Closing this issue.

In response to this:

Closing this since this needs to be opened in the provider repo rather than the upstream repo
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.