aws-cdk/lambda-layer-kubectl-v27: Found CDK v1 deps in your project, even though your "cdkVersion" is 2.x.
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the bug
When using kubectl layers for newer version, CDK complain that the layer still uses CDK V1.
### Expected Behavior
CDk should not complain and the lambda layer library should use CDK v2
### Current Behavior
CDk should not complain and the lambda layer library seems to use CDK v1.
```
👾 default | ts-node --skip-project .projenrc.ts
👾 WARNING: Found CDK v1 deps in your project, even though your "cdkVersion" is 2.x: [@aws-cdk/lambda-layer-kubectl-v27]. Check out https://docs.aws.amazon.com/cdk/v2/guide/migrating-v2.html for more information about using CDK v2 dependencies.
👾 Installing dependencies...
👾 install | yarn install --check-files
```
### Reproduction Steps
Create an EKS cluster with L2 module and pass the lambda layer of any EKS after 1.21.
### Possible Solution
_No response_
### Additional Information/Context
_No response_
### CDK CLI Version
2.118.0
### Framework Version
_No response_
### Node.js Version
v18.18.0
### OS
macOS
### Language
TypeScript
### Language Version
4.9.4
### Other information
_No response_
Contributor guide
Research direction
Start by reproducing an EKS cluster with the L2 module and a kubectl layer for an EKS version after 1.21. Inspect the dependency metadata for aws-cdk/lambda-layer-kubectl-v27 and verify that it uses CDK v2 dependencies. Done means the CDK v1 dependency warning is absent with CDK CLI 2.118.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100