<div dir="ltr">Thanks Flavio for the consideration. I was looking at calico, but this seems to be also a good plugin for container apps that prefers non-NAT/overlay env. It seems to have higher performance/low latency advantages.<br><br>Regards,<br>Jerry</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 15, 2018 at 12:35 AM, Flavio Castelli <span dir="ltr"><<a href="mailto:fcastelli@suse.com" target="_blank">fcastelli@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Next major release of SUSE Container as a Service Platform will use<br>
flannel deployed as a CNI plugin.<br>
<br>
We are currently evaluating other networking solutions. Thanks for your<br>
suggestion, we will take a look also at kube-router.<br>
<br>
Cheers<br>
Flavio<br>
<br>
On 01/12/2018 06:29 PM, Jerry Hwang wrote:<br>
> Hello,<br>
><br>
> Does SUSE have a plan/consideration about kube-router project<br>
> (<a href="https://github.com/cloudnativelabs/kube-router" rel="noreferrer" target="_blank">https://github.com/<wbr>cloudnativelabs/kube-router</a>) vs. CNI vs. flannel?<br>
><br>
> Thanks,<br>
> Jerry<br>
><br>
> On Wed, Dec 20, 2017 at 1:52 PM, Jerry Hwang <<a href="mailto:special011@gmail.com">special011@gmail.com</a><br>
> <mailto:<a href="mailto:special011@gmail.com">special011@gmail.com</a>>> wrote:<br>
><br>
> Nice, thanks Alvaro for the clarification.<br>
><br>
> Jerry<br>
><br>
> On Wed, Dec 20, 2017 at 1:38 PM, Alvaro Saurin<br>
> <<a href="mailto:alvaro.saurin@suse.com">alvaro.saurin@suse.com</a> <mailto:<a href="mailto:alvaro.saurin@suse.com">alvaro.saurin@suse.com</a><wbr>>> wrote:<br>
><br>
><br>
><br>
> When a pod is configured with "hostNetwork: true", the<br>
> applications running in such a pod can directly see the network<br>
> interfaces of the host machine where the pod was started. From<br>
> the networking point of view, it will behave as any other<br>
> application running in the host. And, even if flannel is still<br>
> running in the host, the pod will not be automatically connected<br>
> to that overlay network but use the native routing mechanism.<br>
><br>
> Cheers<br>
><br>
><br>
> Alvaro<br>
><br>
><br>
><br>
><br>
> On 12/20/2017 09:05 PM, Jerry Hwang wrote:<br>
>> Thanks Flavio.<br>
>> So SUSE CaaS v2 networking is flannel (overlay).<br>
>> Regardless I set "hostNetwork: True" for Pod, the inter-nodes<br>
>> traffic will be still encapsulated in udp backend?<br>
>> Any consideration for non-overlay networking solution for v3+?<br>
>><br>
>> Jerry<br>
>><br>
>> On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli<br>
>> <<a href="mailto:fcastelli@suse.com">fcastelli@suse.com</a> <mailto:<a href="mailto:fcastelli@suse.com">fcastelli@suse.com</a>>> wrote:<br>
>><br>
>> On 12/11/2017 05:13 AM, Jerry Hwang wrote:<br>
>> > I have a general question.<br>
>> > CaaS v2 networking is flannel overlay networking using<br>
>> udp encapsulation<br>
>> > for traffic between nodes.<br>
>> > If my app is based on docker "host" networking<br>
>> (net=host), how to make<br>
>> > the app migration from docker to caas/kubernetes env<br>
>> possible?<br>
>><br>
>> You can still tell kubernetes to create a pod that uses<br>
>> the host network:<br>
>><br>
>> kind: Pod<br>
>> spec:<br>
>> hostNetwork: True<br>
>> ...<br>
>><br>
>> However please evaluate whether that makes still sense in<br>
>> the kubernetes<br>
>> context.<br>
>><br>
>> Cheers<br>
>> Flavio<br>
>> ______________________________<wbr>_________________<br>
>> caasp-beta mailing list<br>
>> <a href="mailto:caasp-beta@lists.suse.com">caasp-beta@lists.suse.com</a> <mailto:<a href="mailto:caasp-beta@lists.suse.com">caasp-beta@lists.suse.<wbr>com</a>><br>
>> <a href="http://lists.suse.com/mailman/listinfo/caasp-beta" rel="noreferrer" target="_blank">http://lists.suse.com/mailman/<wbr>listinfo/caasp-beta</a><br>
>> <<a href="http://lists.suse.com/mailman/listinfo/caasp-beta" rel="noreferrer" target="_blank">http://lists.suse.com/<wbr>mailman/listinfo/caasp-beta</a>><br>
>><br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> caasp-beta mailing list<br>
>> <a href="mailto:caasp-beta@lists.suse.com">caasp-beta@lists.suse.com</a> <mailto:<a href="mailto:caasp-beta@lists.suse.com">caasp-beta@lists.suse.<wbr>com</a>><br>
>> <a href="http://lists.suse.com/mailman/listinfo/caasp-beta" rel="noreferrer" target="_blank">http://lists.suse.com/mailman/<wbr>listinfo/caasp-beta</a><br>
>> <<a href="http://lists.suse.com/mailman/listinfo/caasp-beta" rel="noreferrer" target="_blank">http://lists.suse.com/<wbr>mailman/listinfo/caasp-beta</a>><br>
><br>
> --<br>
> Alvaro Saurin <<a href="mailto:alvaro.saurin@suse.com">alvaro.saurin@suse.com</a>> <mailto:<a href="mailto:alvaro.saurin@suse.com">alvaro.saurin@suse.com</a><wbr>><br>
> Senior Software Engineer<br>
> SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: <a href="tel:%2B49-911-74053-0" value="+49911740530">+49-911-74053-0</a>; Fax: <a href="tel:%2B49-911-7417755" value="+499117417755">+49-911-7417755</a> <tel:+49%20911%207417755>; <a href="https://www.suse.com/" rel="noreferrer" target="_blank">https://www.suse.com/</a><br>
> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)<br>
><br>
><br>
><br>
</blockquote></div><br></div>