fix(eks-v2-alpha): ensure kubectl provider and handler functions use the same vpc configuration

[msessa]

Issue # (if applicable)

Closes #34877

Reason for this change

The kubectl Provider function VpcConfig should match the Handler function.

Description of changes

• Ensured the same vpc construct is passed to both Handler and Provider

Description of how you validated changes

• Fixed the tests which were hiding the problem

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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 fails with the following errors:

❌ Fixes must contain a change to an integration test file and the resulting snapshot.

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.

✅ A exemption request has been requested. Please wait for a maintainer's review.

[msessa]

Exemption Request: No functional change to express in an integration test

[vishaalmehrishi]

Nice catch, thank you for the fix!

[vishaalmehrishi]

Re integration tests: I think it would be good to update existing tests/add new tests which verify that the provider and handler lambdas are set up using the same VPC configuration.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 65ea7d8
• Result: FAILED
• Build Logs (available for 30 days)

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