[WIP][Windows] Remove the dependency on kube-proxy

[ruicao93]

Problem

Currently, Antrea on Windows replies on kube-proxy to provide NodePort Service and ClusterIP Service from host. It has been implemented to access ClusterIP Service from Pod. By removing the kube-proxy and implementing the related functions with antrea-proxy, we could take full control of the traffic and make it more efficient. This design is going reuse some implementations already done like service loalbalance in OVS.

Solution

• Support ClusterIP Service access from host. [WIP][Windows] Support ClusterIP Service access from host on Windows with antrea-proxy #1954
• Support NodePort Service access. [WIP][Windows]Antrea Proxy NodePort Service Support #1934
• (WIP) Re-arrange bootstrap order. It would be same as Linux case. Replace KubeProxy Design Draft (Linux Only) #1931

Necessary steps

1. Existing kube-proxy process need to be stoped.
2. Existing service interface used by kube-proxy need to be removed. Because kube-proxy adds service IPs on the interface.

Suggestions

From community meeting on 03/16/2021

• Use br-int instead of routes on host.
• Use Windows VFP framework to function as iptables. It may not be easy to use according to current research.
• For users
  • If NodePort service support from local host is necessary.
  • If there are multiple uplinks on Windows node, can OVS support all of them?
• Cache in-port in flow table for NodePort service from local Pod.
• Is NP support on Windows affected by the design?

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days