Open ledroide opened 1 month ago
Thinking of breaking changes .... this will be a breaking change anyway for users that have set a value for cilium_kube_proxy_replacement in their inventory. I'm afraid there is no solution for them.
Other issue can be in replacing 3 old options disabled/partial/strict with only a boolean choice. I have no idea how to manage this.
We can just remind users about breaking change in the release note.
summary
Cilium v1.16 fails to start in CrashLoopBackOff with this log :
This is due to settings values that have been deprecated since january 2023 in agent: Deprecate --kube-proxy-replacement=partial and agent/helm: Deprecate --kpr=partial|strict|disabled and use --kpr=true|false instead, and not supported anymore since march 2024 for v1.16.0.
Quote :
From cilum release notes :
environment
what should be updated
cilium_kube_proxy_replacement: strict
is changed withcilium_kube_proxy_replacement: true
cilium_kube_proxy_replacement: partial
anddisabled
are both changed withcilium_kube_proxy_replacement: false
I will try to fix it, and then if it succeeds I will sent a pull-request.