Repository for tools and artifacts related to the sig-windows charter in Kubernetes. Scripts to assist kubeadm and wincat and flannel will be hosted here.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Extend the flannel and kube-proxy hostprocess components to support either host-gw or vxlan backends.
Proposal idea
One approach is to abstract backend choice into environment variables and the entrypoint scripts so that one image works for both backend options
extend flannel daemonset with a FLANNEL_BACKEND=host-gw|vxlan environment variable
extend flannel configmap with an additional CNI config for host-gw backend
modify flanneld entrypoint script to render proper CNI config based on FLANNEL_BACKEND environment variable
extend kube-proxy daemonset with a FLANNEL_BACKEND=host-gw|vxlan environment variable
modify kube-proxy entrypoint script startup arguments based on FLANNEL_BACKEND environment variable
Engineers would just need to set FLANNEL_BACKEND env in each manifest.
Additional context
I'm coming from a history of cluster builds that all leveraged flannel host-gw backend and win-bridge cni plugin delegate. I wanted to keep this consistent with new a k8s v1.28 cluster on windows server 2022 nodes.
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Extend the flannel and kube-proxy hostprocess components to support either host-gw or vxlan backends.
Proposal idea
One approach is to abstract backend choice into environment variables and the entrypoint scripts so that one image works for both backend options
FLANNEL_BACKEND=host-gw|vxlanenvironment variableFLANNEL_BACKENDenvironment variableFLANNEL_BACKEND=host-gw|vxlanenvironment variableFLANNEL_BACKENDenvironment variableEngineers would just need to set
FLANNEL_BACKENDenv in each manifest.Additional context
I'm coming from a history of cluster builds that all leveraged flannel host-gw backend and win-bridge cni plugin delegate. I wanted to keep this consistent with new a k8s v1.28 cluster on windows server 2022 nodes.
minimum viable prototype can be found here: https://github.com/Zombro/sig-windows-tools/pull/1/files, sort of shows a rough draft of the diff between your overlay and my bridge
i could spin up a pr if you think it's worthwhile