OperationCode / OperationCode/operationcode_infra
Upgrade to aws-load-balancer-controller v2
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 17
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
We're on the ALB ingress controller (v1). The same project has changed its name to the AWS Load Balancer Controller and very recently cut a v2 release. It's brand new so we should let it bake a while in the wild.
A good reason to upgrade to v2 is IngressGroup feature, which lets you share ALBs between namespaces. This would allow us to reduce our ALBs down to just 1, saving some monthly spend. Described here
Handy links:
- Installation docs from AWS: https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html
- GH releases page: https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases
- v1 to v2 migration guide: https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/guide/upgrade/migrate_v1_v2.md
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked v1-to-v2 migration guide, the AWS installation documentation, and the controller's releases page to understand the required upgrade steps. Review the repository's current ALB ingress controller configuration, then verify that the deployment uses v2 and that the intended IngressGroup setup can reduce ALBs as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100