[aws-eks] Support passing memory config to Kubectl Lambda layer #11248
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
duplicate
This issue is a duplicate.
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p2
Today the kubectl Lambda layer has a hardcoded value of 256MB as seen here: https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-eks/lib/kubectl-provider.ts#L78
The problem is that I install a helm chart (with version 1.70 and the Lambda exhausts its memory. It can go up to 370MB in a test run that I've done. So making this configurable, or if anything bump the hardcoded value to 512 instead of 256, will avoid failing of helm charts.
You can see helm dies prematurely because it logs the following message:
And then the subprocess will fail with a non-zero exit code causing the CDK run to fail.
On a successful run the Lamba logs what you'd expect:
And the last line of the Lambda run shows the memory usage well exceeding 256MB:
vs
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: