feat(eks): add L2 constructs to support EKS Hybrid Nodes

[abhay-krishna]

Issue # (if applicable)

Closes #32362.

Reason for this change

This change allows users to specify the networking primitives for an EKS Hybrid nodes cluster through L2 constructs.

Description of changes

This PR introduces two new top-level fields called remoteNodeNetworks and remotePodNetworks in the Cluster construct. Together, these allow users to specify the exact CIDRs ranges they want to use for their on-premises nodes and (optionally) pods. The Hybrid nodes feature requires that none of the node and pod CIDRs overlap with each other so I have also added validations for that.

Description of how you validated changes

Added unit tests with different testcases involving different remote network configurations.

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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.92%. Comparing base (1d15d49) to head (3127242).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #32389   +/-   ##
=======================================
  Coverage   80.92%   80.92%           
=======================================
  Files         236      236           
  Lines       14255    14255           
  Branches     2491     2491           
=======================================
  Hits        11536    11536           
  Misses       2434     2434           
  Partials      285      285           

Flag	Coverage Δ
suite.unit	80.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	79.74% <ø> (ø)
packages/aws-cdk-lib/core	82.20% <ø> (ø)

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

[abhay-krishna]

@khushail Can you review this PR? The large diff is due to the several integration test snapshots being updated, I would suggest filtering *.ts files to see the actual changes I made for the Hybrid nodes feature. Thank you!

[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.

[abhay-krishna]

@khushail all the GitHub actions passed except the CodeQL scanning results. It's complaining on integration test snapshot code that's autogenerated. Do you have any pointers on how to resolve this?

[khushail]

@abhay-krishna , integration test snapshots need to be generated and submitted by you. Here is a guide on how to do that -https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md#running-integration-tests.

You might want to look for existing closed PRs for additional help on generating these snapshot tests. Hope that would be helpful.

[abhay-krishna]

@abhay-krishna , integration test snapshots need to be generated and submitted by you. Here is a guide on how to do that -https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md#running-integration-tests.

You might want to look for existing closed PRs for additional help on generating these snapshot tests. Hope that would be helpful.

@khushail Yes I understood that part, and I have submitted those integration test changes and snapshots too. However the CodeQL scanner is failing a check on one of those snapshots. Since these snapshots are generated code and I'm not handwriting them, I am not sure how to go about fixing them.

Pull request has been modified.

[GavinZZ]

One minor comment and I'm happy to approve. Thank you!

Pull request has been modified.

Pull request has been modified.

[GavinZZ]

LGTM, thank you for addressing all the comments!

[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]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 3127242
• 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).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.