Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exposing NodePort Services might end up failing when port is already occupied #489

Open
pmalek opened this issue Jan 9, 2023 · 0 comments
Open

Exposing NodePort Services might end up failing when port is already occupied #489

pmalek opened this issue Jan 9, 2023 · 0 comments

Comments

@pmalek
Copy link
Member

pmalek commented Jan 9, 2023

Problem statement

When a port is already occupied on a node then exposing a NodePort Service 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pmalek