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
karpenterAddonProps requires a 'namespace' parameter to successfully create controller addon role. This parameter is not included in the addon props and therefore silently fails. When it fails it does not create a namespace or the controller role required Karpenter.
Describe the bug
karpenterAddonProps requires a 'namespace' parameter to successfully create controller addon role. This parameter is not included in the addon props and therefore silently fails. When it fails it does not create a namespace or the controller role required Karpenter.
https://github.com/aws-quickstart/cdk-eks-blueprints/blob/main/lib/addons/karpenter/index.ts#L468
This was implemented here - commit f337610
Expected Behavior
When not defining a namespace, expect an assertion error thrown or sensible default (e.g karpenter) namespace to be created.
Also expect namespace to be defined within the karpenterAddonProps.
Current Behavior
Defining a basic karpenterAddOn does not create a namespace, karpenter controller or controller role.
If you then define an undocumented namespace var it does create a namespace and controller role (as expected).
This required tracking down the variable needed here - https://github.com/aws-quickstart/cdk-eks-blueprints/blob/main/lib/addons/karpenter/index.ts#L468
Reproduction Steps
Possible Solution
!
notationAdditional Information/Context
No response
CDK CLI Version
2.1007.0
EKS Blueprints Version
No response
Node.js Version
v22.11.0
Environment details (OS name and version, etc.)
Github codespace
Other information
No response
The text was updated successfully, but these errors were encountered: