Reimplement Cilium feature dependency logic

[hoferbeck]

Hi @nilsgoebl

I built logic so that when, for example, the Cilium Bandwidth Manager is active, it also enables the Kubeproxy Replacement and BPF routing.
See

gubernat/roles/kubernetes/templates/cilium-helm-values.yaml.j2

Line 109 in c977523

{% if cilium.bandwidthManager | default("false", true) is true or cilium.l2announcements.enabled | default("false", true) is true %}

https://docs.cilium.io/en/latest/network/kubernetes/bandwidth-manager/

Somehow this logic got lost in the upgrade to Gubernat v2 (was that intentional?)

If not, it would be nice to re-add this logic. During the upgrade of one of my clusters it removed KubeProxy part of Cilium while the Cilium Bandwidth Manager remained active, which caused some connection timeouts.

[nilsgoebl]

Hey @hoferbeck

In gubernat v2, this was put behind a separate flag:

gubernat/roles/kubernetes/templates/cilium-helm-values.yaml.j2

Line 105 in a48b588

{% if cilium.replaceKubeProxy | default("false", true) is true %}

I'm not 100% sure why we did this, maybe it was just for more control, or because @pflaeging didn't love the idea of replacing kube-proxy?