Broken ClusterConfig
with dynamic config results in wiping system services
#4721
Labels
ClusterConfig
with dynamic config results in wiping system services
#4721
Before creating an issue, make sure you've checked the following:
Platform
No response
Version
No response
Sysinfo
`k0s sysinfo`
What happened?
In case we end up having broken config in dynamic
ClusterConfig
, e.g. bothexternalAddress
and NLLB enabled, the additional controller can wipe out the system services such as kube-router.In this case the second controller joining had empty stacks for all system services. At some point in time it had, supposedly, been the leader for a bit and thus applied some of the stacks. The stacks being empty, kube-router and some other stacks were completely removed.
Steps to reproduce
--dynamic-config
and some configClusterConfig
. Invalid from k0s point of view but valid (enough) to be accepted by the API--dynamic-config
Expected behavior
When we receive invalid dynamic config we would need to stop reconciling it completely to not possibly borking already functioning cluster completely.
Actual behavior
No response
Screenshots and logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: