aws-samples / aws-samples/eks-workshop-v2
Clusters do not need RemoteNodeCidr and RemotePodCidr set all the time now
- Dominant language
- HCL
- Stars
- 626
- Forks
- 613
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 9
Description
### What would you like to be added?
EKS Workshop adds RemoteNodeCidr and RemotePodCidr to every cluster created, regardless of whether or not the EKS Hybrid Nodes module will be run. This was because it was not possible to modify existing clusters, so this compromise was put in place. We can now modify clusters to add RemoteNodeCidr and RemotePodCidr after creation.
The EKS Hybrid Nodes module should modify the cluster to add the cidrs at the start of the module, rather than at cluster creation in every workshop.
### Why is this needed?
This is really a nice-to-have. I don't know how well Terraform will handle adding these fields to the cluster that was created previously by eksctl.
Contributor guide
Research direction
Start with the EKS Hybrid Nodes module and the cluster creation configuration that currently sets RemoteNodeCidr and RemotePodCidr. Check how Terraform handles adding these fields to an existing cluster, then verify that the CIDRs are applied when the module starts and are no longer set for every cluster by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100