k0s
k0s copied to clipboard
Add config option to set bind address for all components.
This enables to bind all components, that listen for traffic, only to certain interface on the host.
Draft as we're waiting for reactions on https://github.com/kubernetes-sigs/apiserver-network-proxy/pull/363 In the meantime konnectivity is build from my custom branch which has the bind-address flags.
Signed-off-by: Jussi Nummelin [email protected]
Description
Fixes #1150 , the ability to use VIP+LB on controller nodes.
Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation update
How Has This Been Tested?
- [ ] Manual test
- [x] Auto test added
Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] My commit messages are signed-off
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published in downstream modules
- [ ] I have checked my code and corrected any misspellings
check-tunneledkas
smoke test failing as my custom branch for konnectivity bind-address does not have the tunneling built in
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
@jnummelin hi! what's the status of this PR? The linked PR has been merged and released and appears to be present in the currently used version of konnectivity
.
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
@jnummelin are we planning to merge this?
The PR is marked as stale since no activity has been recorded in 30 days
The PR is marked as stale since no activity has been recorded in 30 days
This pull request has merge conflicts that need to be resolved.
closing this in favor of the newer in-flight PR
That PR being https://github.com/k0sproject/k0s/pull/3824 presumably