(eks): eks.Addon missing ConfigurationValues property

[markusl]

Describe the feature

The EKS documentation explains addon usage: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_eks-readme.html

new eks.Addon(this, 'Addon', {
  cluster,
  addonName: 'aws-guardduty-agent',
  addonVersion: 'v1.6.1',
  // whether to preserve the add-on software on your cluster but Amazon EKS stops managing any settings for the add-on.
  preserveOnDelete: false,
});

However, it seems to be missing the ConfigurationValues property which makes configuring the addon impossible https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-eks-addon.html#cfn-eks-addon-configurationvalues

Use Case

As a user, I would like to configure addons as explained in the addon-specific documentation https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing

Proposed Solution

No response

Other Information

Add the configuration property

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.1006.0 (build a3b9762)

Environment details (OS name and version, etc.)

all

[pahud]

Hi markusl,

Thanks for reporting this feature request for the AWS CDK EKS module!

Issue Summary:

Theeks.Addon L2 construct in aws-cdk-lib currently lacks the configurationValues property. This prevents users from providing custom configurations to EKS addons directly through the CDK, even though the underlying CloudFormation resource (AWS::EKS::Addon) supports it.

Analysis:

I've reviewed the source code (packages/aws-cdk-lib/aws-eks/lib/addon.ts) and confirmed that the AddonProps interface and the Addon constructor do not handle the configurationValues parameter.

Current Behavior vs. Expected Behavior:

Currently, the eks.Addon construct only allows setting basic properties like addonName, addonVersion, and preserveOnDelete, resulting in addons being deployed with their default configurations. The expected behavior is to allow passing a JSON string via configurationValues to customize the addon deployment, similar to how it's done in CloudFormation.

As the team is actively working on the aws-eks-v2-alpha module, we welcome PRs to address this in both v1 and v2 modules.