Jing Zhang

Hi, I had tried to put more information for the PR in the commit message but messed up the format, so they did not show up. Major reasons for this...

Hi, This PR is to solve the real issue in deployment scenario where VMs are on flat networks. VMs are assigned with trunk ports, IPs are assigned on the subports....

Hi, (1) Below are the excerpts from logs without and with the PR: === without the PR === I0525 15:39:22.462829 1 node_controller.go:325] Initializing node mycluster-01-control-01 with cloud provider E0525 15:39:24.132876...

Hi, (1) It is because the nodeIp 10.10.10.50 is on the vlan interface (subport), not on the trunk port (2) Just to be sure I follow you...I have assumed this...

Hi, (1) This PR is NOT to remove the IPs assigned on the ports (trunk port) directly attached to the instance, this is why I said this PR is transparent...

Hi, Not sure what exactly is not clear to you. Let me try again by breaking down the details step-by-step: (1) VMs are vlan-aware. (2) VMs are attached with trunk...

Hi, (1) Node IP is on on the sub-port, not on the trunk ports. (2) IPs on the trunk ports are filtered by internal-network-name. We expect to verify Octivia w/...

Initial PR to get reviewers agreement and guidance. Detailed design will be populated after that.

Completed the KEP writing. Created the initial kubelet PR to get reviewers comments and guidance. More test cases will be added.

Updated "RIsks and Mitigations" section for impact on reduced shared pool size. Please review and advise.