(aws-eks): Use the new Managed Cluster Add-Ons for AWS CNI, kubeproxy and CoreDNS
Open
@aws-cdk/aws-eks
@aws-cdk/aws-eks-v2-alpha
effort/medium
feature-request
p2
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
Now that EKS has Managed Add-On for the three things that come with an EKS cluster (CNI, kubeproxy and CoreDNS) it'd be great if CDK's Cluster construct could leverage them with IRSA as well as help with their upgrade to new versions after the corresponding EKS version upgrades are done to the cluster etc.
Contributor guide
Research direction
Start by inspecting CDK's Cluster construct and AWS EKS managed add-on and IRSA documentation. Define the expected handling of CNI, kubeproxy, and CoreDNS, including upgrades after EKS version changes, then identify the relevant tests and completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100