(addons-karpenter 0.13.2): Fails to deploy when using Fargate ONLY for Karpenter namespace

javydekoning commented 2 years ago

Describe the bug

When deploying a stack with only the below as cluster provider Karpenter fails to deploy (Custom Resource Timesout).

    const clusterProvider = new blueprints.GenericClusterProvider({
      version: eks.KubernetesVersion.V1_21,
      fargateProfiles: {
        karpenter: {
          fargateProfileName: 'karpenter',
          selectors: [{ namespace: 'karpenter' }],
        },
      },
    });

This is likely related to: https://github.com/aws/karpenter/issues/2186 and could be fixed by overriding the values.yml of the helm chart.

Expected Behavior

I expect Karpenter to deploy to Fargate and then spin up worker nodes for the kube-system (and other) namespaces.

Current Behavior

Deployment fails

Error: b'Release "blueprints-addon-karpenter" does not exist. Installing it now.
Error: timed out waiting for the condition\n'

Reproduction Steps

Deploy with a generic cluster-provider as provided above.

Possible Solution

Clarify in documentation, override values OR wait for a fix in the Karpenter helm repo.

Additional Information/Context

No response

CDK CLI Version

Not Relevant

EKS Blueprints Version

1.1.0

Node.js Version

Not Relevant

Environment details (OS name and version, etc.)

Not Relevant

Other information

Reproduced as per discussion with @youngjeong46

youngjeong46 commented 2 years ago

@javydekoning I will submit a PR this afternoon to resolve this per documentation and upgrade default to 0.14.0. It will be released as part of 1.2.0.

youngjeong46 commented 2 years ago

This has been resolved. Closing the issue.

aws-quickstart / cdk-eks-blueprints