kOps doesn't tag API server NLBs
Open
kind/feature
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
/kind feature
The ENIs that AWS provisions for the API server NLB (description ELB net//...) are not tagged by kOps, unlike the rest of the cluster's networking resources. It would be great if kOps could apply tags to them.
Contributor guide
Research direction
Start by tracing kOps's AWS API server NLB handling and compare it with the existing tagging logic for cluster networking resources. Confirm which ENIs have descriptions matching ELB net//... and verify that the intended tags are applied to those ENIs without changing other resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100