<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
When a pod is configured with "hostNetwork: true", the applications
running in such a pod can directly see the network interfaces of the
host machine where the pod was started. From the networking point of
view, it will behave as any other application running in the host.
And, even if flannel is still running in the host, the pod will not
be automatically connected to that overlay network but use the
native routing mechanism.<br>
<br>
Cheers<br>
<br>
<br>
Alvaro<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 12/20/2017 09:05 PM, Jerry Hwang
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANrne0TJc8F_Ps4KTPcJvHFNWd+12-3a6YrZ69JjYFtVWpPgzQ@mail.gmail.com">
<div dir="ltr">
<div>Thanks Flavio.</div>
<div>So SUSE CaaS v2 networking is flannel (overlay).</div>
<div>Regardless I set "hostNetwork: True" for Pod, the
inter-nodes traffic will be still encapsulated in udp backend?</div>
<div>Any consideration for non-overlay networking solution for
v3+?<br>
<br>
Jerry</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec 20, 2017 at 1:26 AM, Flavio
Castelli <span dir="ltr"><<a
href="mailto:fcastelli@suse.com" target="_blank"
moz-do-not-send="true">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">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
udp encapsulation<br>
> for traffic between nodes.<br>
> If my app is based on docker "host" networking
(net=host), how to make<br>
> the app migration from docker to caas/kubernetes env
possible?<br>
<br>
You can still tell kubernetes to create a pod that uses the
host network:<br>
<br>
kind: Pod<br>
spec:<br>
hostNetwork: True<br>
...<br>
<br>
However please evaluate whether that makes still sense in
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"
moz-do-not-send="true">caasp-beta@lists.suse.com</a><br>
<a href="http://lists.suse.com/mailman/listinfo/caasp-beta"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.suse.com/mailman/<wbr>listinfo/caasp-beta</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
caasp-beta mailing list
<a class="moz-txt-link-abbreviated" href="mailto:caasp-beta@lists.suse.com">caasp-beta@lists.suse.com</a>
<a class="moz-txt-link-freetext" href="http://lists.suse.com/mailman/listinfo/caasp-beta">http://lists.suse.com/mailman/listinfo/caasp-beta</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Alvaro Saurin <a class="moz-txt-link-rfc2396E" href="mailto:alvaro.saurin@suse.com"><alvaro.saurin@suse.com></a>
Senior Software Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; <a class="moz-txt-link-freetext" href="https://www.suse.com/">https://www.suse.com/</a>
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
</pre>
</body>
</html>