Kong / Kong/kubernetes-testing-framework
Exposing NodePort Services might end up failing when port is already occupied
- Dominant language
- Go
- Stars
- 44
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
## Problem statement
When a port is already occupied on a node then [exposing a NodePort Service](https://github.com/Kong/kubernetes-testing-framework/blob/d0f8f0b1c588224b64cfee772fff3e73fb365db9/pkg/clusters/addons/kong/addon.go#L550) will fail the cluster setup.
Example: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/3876274683/jobs/6609910543#step:6:358
> Error: tests failed: failed to deploy addon kong: Error: INSTALLATION FAILED: Service "ingress-controller-kong-admin" is invalid: spec.ports[0].nodePort: Invalid value: 32080: provided port is already allocated
Contributor guide
Research direction
Start at pkg/clusters/addons/kong/addon.go around line 550 and use the linked CI failure as context for the NodePort exposure path. Determine how an occupied node port should be handled and verify that cluster setup no longer fails when the port is already allocated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100