These are the known issues in off-the-shelf Kubernetes.

 

A CNCF SIG was formed to address the issue of “no isolation among multi-tenant”; data path performance is being addressed by other open-source projects, such as Cilium. The slogan in Cilium’s kubecon booth is “Liberating Kubernetes from kube-proxy and iptables”.

 

Thanks,

Forrest

 

From: Xie, Cindy <cindy.xie@intel.com>
Sent: Tuesday, November 19, 2019 9:35 PM
To: Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io; Zhao, Forrest <forrest.zhao@intel.com>; Le, Huifeng <huifeng.le@intel.com>
Subject: RE: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question

 

Forrest, Huifeng,

Do you understand the issue below and if we have any plan to address it?

 

Cindy Xie

IAGS

One Intel Champion Badge

 

From: Jones, Bruce E <bruce.e.jones@intel.com>
Sent: Wednesday, November 20, 2019 10:39 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question

 

I am at Kubecon this week and met with a potential partner who is interested in StarlingX.  He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues.   I don’t know enough about Networking to answer his questions.

 

In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S.  He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important.

 

If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner.

 

Thank you!

 

           brucej