-
Couldn't load subscription status.
- Fork 442
Description
Is your feature request related to a problem? Please describe.
Currently, the Konnectivity agent's host network configuration is only controlled internally when node-local load balancing is enabled. This feature request adds explicit configuration support to allow users to control whether the Konnectivity agent should use host networking independently of the node-local load balancing feature.
There are scenarios where users need to run the Konnectivity agent with hostNetwork: true for specific networking requirements or troubleshooting purposes, independent of node-local load balancing configuration.
A Key scenario include:
- CNI Installation Deadlock Prevention: In certain network environments, CNI installation may not be possible due to network restrictions, creating a deadlock where neither Konnectivity agents nor CNI can establish connectivity. Running Konnectivity agents with host networking can break this deadlock by allowing initial cluster communication.
Describe the solution you would like
Add a new hostNetwork field to the KonnectivitySpec configuration that allows explicit control over the Konnectivity agent's network mode.
Configuration API Changes:
- Add HostNetwork bool field to KonnectivitySpec in pkg/apis/k0s/v1beta1/konnectivity.go
- Default value: false (maintains backward compatibility)
- Kubebuilder annotations for proper CRD generation
Describe alternatives you've considered
No response
Additional context
No response