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.

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

feat: bump kube-service-exposer to v0.2.0 #552

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

utkuozdemir
Copy link
Member

Contains the fix for the goroutine leak on port conflict, see: https://github.com/siderolabs/kube-service-exposer/releases/tag/v0.2.0

Also, use the new --disallowed-host-port-ranges flag to prevent a set of known ports used by Talos to not be used by the exposer.

Closes #502.

Contains the fix for the goroutine leak on port conflict, see: https://github.com/siderolabs/kube-service-exposer/releases/tag/v0.2.0

Also, use the new `--disallowed-host-port-ranges` flag to prevent a set of known ports used by Talos to not be used by the exposer.

Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
@utkuozdemir
Copy link
Member Author

/m

@talos-bot talos-bot merged commit 1cb1080 into siderolabs:main Aug 15, 2024
19 checks passed
@utkuozdemir utkuozdemir deleted the bump-kube-service-exposer branch August 15, 2024 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kube service exposer should gracefully handle ports being in use
3 participants