fix(eks): use Python 3.10 runtime for kubectl-provider

[plumdog]

Use Python 3.10 runtime for kubectl-provider. The previously used version is now EOL and will be deprecated soon in AWS Lambda.

Note that while newer Python runtime versions are already available, 3.10 is the newest runtime available in all partitions (including GovCloud and CN).

Closes #26994.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

[plumdog]

Clarification Request

• Maybe this is not a feature? Regardless, I don't think it warrants a change to the README.
• It doesn't appear that the unit tests check for this
• I'm unable to run the integration tests.

[plumdog]

I lieu of running the integration tests, I have modified a kubectl provider Lambda deployed by CDK and found that it was able to run and upgrade a helm chart for me, so I am confident it works.

[plumdog]

Exemption Request

[mrgrain]

Thanks @plumdog I'll pick this up soon. Apologies for the delay. We were operating with reduced capacity the last couple weeks.

[mrgrain]

Is Python 3.11 the right runtime? I couldn't find anything confirming which Lambda runtimes are available in which regions. The blog post https://aws.amazon.com/about-aws/whats-new/2023/07/aws-lambda-python-3-11/ says "The Python 3.11 runtime is available in all Regions where Lambda is available, except for China and GovCloud Regions." which was published 27th July 2023.

We have to use Python 3.10 for now. Once Python 3.11 is cleared for the remaining regions, we can switch over.

I have not run the integration tests because - based on https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md#integration-tests - I understand doing so will attempt to deploy some AWS resources. I don't know what the billing implications of this would be, but I don't have an AWS account where I'm happy to chance this.

I can do this.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

Pull request has been modified.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 7e2be90
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).