The current POC has a services implementation, where an ODL Kube Proxy agent is running on all kubernetes nodes, and is responsible for load balancing the requests to the respective pods. The odl kube proxy programs openflow rules on the OVS, based on the load balancing decision taken locally.
This implementation needs to be reviewed from a scalability and functionality perspective. If the implementation looks good, we can treat services implementation as completed for Neon.
The current services Services. The initial focus will be to support NodePort and ClusterIP.
Do we want to continue with iptables? That would allow us to continue using the LoadBalancer. Or should NetVirt implement a load balancer?
Faseela K
Medium
The current POC has a services implementation, where an ODL Kube Proxy agent is running on all kubernetes nodes, and is responsible for load balancing the requests to the respective pods. The odl kube proxy programs openflow rules on the OVS, based on the load balancing decision taken locally.
This implementation needs to be reviewed from a scalability and functionality perspective. If the implementation looks good, we can treat services implementation as completed for Neon.
The current services Services. The initial focus will be to support NodePort and ClusterIP.
Do we want to continue with iptables? That would allow us to continue using the LoadBalancer. Or should NetVirt implement a load balancer?