From special011 at gmail.com Fri Jan 12 10:29:55 2018 From: special011 at gmail.com (Jerry Hwang) Date: Fri, 12 Jan 2018 09:29:55 -0800 Subject: [caasp-beta] caas v2 networking In-Reply-To: References:

<538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com> Message-ID: Hello, Does SUSE have a plan/consideration about kube-router project ( https://github.com/cloudnativelabs/kube-router) vs. CNI vs. flannel? Thanks, Jerry On Wed, Dec 20, 2017 at 1:52 PM, Jerry Hwang wrote: > Nice, thanks Alvaro for the clarification. > > Jerry > > On Wed, Dec 20, 2017 at 1:38 PM, Alvaro Saurin > wrote: > >> >> >> 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. >> >> Cheers >> >> >> Alvaro >> >> >> >> >> On 12/20/2017 09:05 PM, Jerry Hwang wrote: >> >> Thanks Flavio. >> So SUSE CaaS v2 networking is flannel (overlay). >> Regardless I set "hostNetwork: True" for Pod, the inter-nodes traffic >> will be still encapsulated in udp backend? >> Any consideration for non-overlay networking solution for v3+? >> >> Jerry >> >> On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli >> wrote: >> >>> On 12/11/2017 05:13 AM, Jerry Hwang wrote: >>> > I have a general question. >>> > CaaS v2 networking is flannel overlay networking using udp >>> encapsulation >>> > for traffic between nodes. >>> > If my app is based on docker "host" networking (net=host), how to make >>> > the app migration from docker to caas/kubernetes env possible? >>> >>> You can still tell kubernetes to create a pod that uses the host network: >>> >>> kind: Pod >>> spec: >>> hostNetwork: True >>> ... >>> >>> However please evaluate whether that makes still sense in the kubernetes >>> context. >>> >>> Cheers >>> Flavio >>> _______________________________________________ >>> caasp-beta mailing list >>> caasp-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/caasp-beta >>> >> >> >> >> _______________________________________________ >> caasp-beta mailing listcaasp-beta at lists.suse.comhttp://lists.suse.com/mailman/listinfo/caasp-beta >> >> >> -- >> Alvaro Saurin >> Senior Software Engineer >> SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755 <+49%20911%207417755>; https://www.suse.com/ >> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sat Jan 13 11:50:48 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sat, 13 Jan 2018 10:50:48 -0800 Subject: [caasp-beta] velum troubleshoot Message-ID: Hello, Does anyone have a general guideline where or how to check velum? I always observe this message in the browser after admin node update (v2) > We're sorry, but something went wrong. > If you are the application owner check the logs for more information. Eventually I can get back to the admin node (velum), but sometimes it takes long, and I thought if I have a list to check or monitor, it'd useful. And I noticed I can't get to k8s cluster via kubectl (from my local machine) during admin node upgrade & reboot, is it expected? Jerry note: this is to look for some general idea or share, not a support request. -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sat Jan 13 14:02:12 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sat, 13 Jan 2018 13:02:12 -0800 Subject: [caasp-beta] velum troubleshoot In-Reply-To: <1515876628007.92646@smartodds.co.uk> References: <1515876628007.92646@smartodds.co.uk> Message-ID: Ah right, all run in container on kubernetes. Thanks, Jerry On Sat, Jan 13, 2018 at 12:50 PM, Liam McCafferty < Liam.McCafferty at smartodds.co.uk> wrote: > Hi Jerry, > > > I always put this down to the fact the node has just rebooted, However if > you wish to view the velum logs it runs inside a container on the admin > node you can find this container via using a docker ps command then use a > docker logs command to get the log output for the container. > > > > Regards, > > > Liam > ------------------------------ > *From:* caasp-beta-bounces at lists.suse.com suse.com> on behalf of Jerry Hwang > *Sent:* 13 January 2018 18:50 > *To:* caasp-beta at lists.suse.com > *Subject:* [caasp-beta] velum troubleshoot > > Hello, > > Does anyone have a general guideline where or how to check velum? > > I always observe this message in the browser after admin node update (v2) > > We're sorry, but something went wrong. > > If you are the application owner check the logs for more information. > > Eventually I can get back to the admin node (velum), but sometimes it > takes long, and I thought if I have a list to check or monitor, it'd useful. > > And I noticed I can't get to k8s cluster via kubectl (from my local > machine) during admin node upgrade & reboot, is it expected? > > Jerry > > note: this is to look for some general idea or share, not a support > request. > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sat Jan 13 14:11:39 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sat, 13 Jan 2018 13:11:39 -0800 Subject: [caasp-beta] velum troubleshoot In-Reply-To: <1515877672987.7123@smartodds.co.uk> References: <1515876628007.92646@smartodds.co.uk> <1515877672987.7123@smartodds.co.uk> Message-ID: Right, that is also a good point. (I too much focused on the general idea :)) And it seems I can't get to k8s cluster via kubectl (from my local machine) during admin node upgrade & reboot, is it expected? Thanks, Jerry On Sat, Jan 13, 2018 at 1:07 PM, Liam McCafferty < Liam.McCafferty at smartodds.co.uk> wrote: > No Velum runs on standard docker on the caas admin node ( along with a > salt master and a mariadb and various other containers ) where as > kubernetes only runs on the master and worker nodes. > > > Hope this helps > > > Regards, > > > Liam > ------------------------------ > *From:* Jerry Hwang > *Sent:* 13 January 2018 21:02 > *To:* Liam McCafferty > *Cc:* caasp-beta at lists.suse.com > *Subject:* Re: [caasp-beta] velum troubleshoot > > Ah right, all run in container on kubernetes. > > Thanks, > Jerry > > On Sat, Jan 13, 2018 at 12:50 PM, Liam McCafferty < > Liam.McCafferty at smartodds.co.uk> wrote: > >> Hi Jerry, >> >> >> I always put this down to the fact the node has just rebooted, However if >> you wish to view the velum logs it runs inside a container on the admin >> node you can find this container via using a docker ps command then use a >> docker logs command to get the log output for the container. >> >> >> >> Regards, >> >> >> Liam >> ------------------------------ >> *From:* caasp-beta-bounces at lists.suse.com > .com> on behalf of Jerry Hwang >> *Sent:* 13 January 2018 18:50 >> *To:* caasp-beta at lists.suse.com >> *Subject:* [caasp-beta] velum troubleshoot >> >> Hello, >> >> Does anyone have a general guideline where or how to check velum? >> >> I always observe this message in the browser after admin node update (v2) >> > We're sorry, but something went wrong. >> > If you are the application owner check the logs for more information. >> >> Eventually I can get back to the admin node (velum), but sometimes it >> takes long, and I thought if I have a list to check or monitor, it'd useful. >> >> And I noticed I can't get to k8s cluster via kubectl (from my local >> machine) during admin node upgrade & reboot, is it expected? >> >> Jerry >> >> note: this is to look for some general idea or share, not a support >> request. >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sat Jan 13 14:30:27 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sat, 13 Jan 2018 13:30:27 -0800 Subject: [caasp-beta] velum troubleshoot In-Reply-To: <1515878635948.68938@smartodds.co.uk> References: <1515876628007.92646@smartodds.co.uk> <1515877672987.7123@smartodds.co.uk> <1515878635948.68938@smartodds.co.uk> Message-ID: Okay, what you described is also what I expected. Thanks for the idea. Regards, Jerry On Sat, Jan 13, 2018 at 1:23 PM, Liam McCafferty < Liam.McCafferty at smartodds.co.uk> wrote: > I have never noticed this before so I just rebooted my admin node and I > can confirm I can still communicate via kubectl to the master node. > > > I have also checked my kube config in ~/.kube/config and I can > see that the cluster server is set to the master server. does > your kubeconfig point to your master node? Upon checking my admin node I > see it also that it has the haproxy k8 containers which I believe deal > with routing to the k8 api. so if your config is pointed to your admin node > that would make sense that you cant reach the api server. > > > > Cheers, > > > Liam > > > > ------------------------------ > *From:* Jerry Hwang > *Sent:* 13 January 2018 21:11 > *To:* Liam McCafferty > *Cc:* caasp-beta at lists.suse.com > *Subject:* Re: [caasp-beta] velum troubleshoot > > Right, that is also a good point. (I too much focused on the general idea > :)) > > And it seems I can't get to k8s cluster via kubectl (from my local > machine) during admin node upgrade & reboot, is it expected? > > Thanks, > Jerry > > On Sat, Jan 13, 2018 at 1:07 PM, Liam McCafferty < > Liam.McCafferty at smartodds.co.uk> wrote: > >> No Velum runs on standard docker on the caas admin node ( along with a >> salt master and a mariadb and various other containers ) where as >> kubernetes only runs on the master and worker nodes. >> >> >> Hope this helps >> >> >> Regards, >> >> >> Liam >> ------------------------------ >> *From:* Jerry Hwang >> *Sent:* 13 January 2018 21:02 >> *To:* Liam McCafferty >> *Cc:* caasp-beta at lists.suse.com >> *Subject:* Re: [caasp-beta] velum troubleshoot >> >> Ah right, all run in container on kubernetes. >> >> Thanks, >> Jerry >> >> On Sat, Jan 13, 2018 at 12:50 PM, Liam McCafferty < >> Liam.McCafferty at smartodds.co.uk> wrote: >> >>> Hi Jerry, >>> >>> >>> I always put this down to the fact the node has just rebooted, However >>> if you wish to view the velum logs it runs inside a container on the admin >>> node you can find this container via using a docker ps command then use a >>> docker logs command to get the log output for the container. >>> >>> >>> >>> Regards, >>> >>> >>> Liam >>> ------------------------------ >>> *From:* caasp-beta-bounces at lists.suse.com >> .com> on behalf of Jerry Hwang >>> *Sent:* 13 January 2018 18:50 >>> *To:* caasp-beta at lists.suse.com >>> *Subject:* [caasp-beta] velum troubleshoot >>> >>> Hello, >>> >>> Does anyone have a general guideline where or how to check velum? >>> >>> I always observe this message in the browser after admin node update (v2) >>> > We're sorry, but something went wrong. >>> > If you are the application owner check the logs for more information. >>> >>> Eventually I can get back to the admin node (velum), but sometimes it >>> takes long, and I thought if I have a list to check or monitor, it'd useful. >>> >>> And I noticed I can't get to k8s cluster via kubectl (from my local >>> machine) during admin node upgrade & reboot, is it expected? >>> >>> Jerry >>> >>> note: this is to look for some general idea or share, not a support >>> request. >>> >>> ______________________________________________________________________ >>> This email has been scanned by the Symantec Email Security.cloud service. >>> For more information please visit http://www.symanteccloud.com >>> ______________________________________________________________________ >>> >>> This e-mail and any files transmitted with it are confidential and may >>> be legally privileged. If you receive it in error or are not the intended >>> recipient you must not copy, distribute or take any action in reliance upon >>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>> 0077 <+44%2020%207482%200077> and delete the material from your >>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>> registered with the Registrar of Companies for England and Wales with >>> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >>> Highgate Road, London NW5 1TL >>> >>> >>> ______________________________________________________________________ >>> This email has been scanned by the Symantec Email Security.cloud service. >>> For more information please visit http://www.symanteccloud.com >>> ______________________________________________________________________ >>> >>> This e-mail and any files transmitted with it are confidential and may >>> be legally privileged. If you receive it in error or are not the intended >>> recipient you must not copy, distribute or take any action in reliance upon >>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>> 0077 <+44%2020%207482%200077> and delete the material from your >>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>> registered with the Registrar of Companies for England and Wales with >>> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >>> Highgate Road, London NW5 1TL >>> >>> >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > This e-mail and any files transmitted with it are confidential and may be > legally privileged. If you receive it in error or are not the intended > recipient you must not copy, distribute or take any action in reliance upon > it. Instead, please notify us immediately by telephoning +44 (20) 7482 > 0077 <+44%2020%207482%200077> and delete the material from your systems. > Smartodds is a business carried on by Smartodds Limited, a company > registered with the Registrar of Companies for England and Wales with > number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 > Highgate Road, London NW5 1TL > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sat Jan 13 21:00:10 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sat, 13 Jan 2018 20:00:10 -0800 Subject: [caasp-beta] velum troubleshoot In-Reply-To: References: <1515876628007.92646@smartodds.co.uk> <1515877672987.7123@smartodds.co.uk> <1515878635948.68938@smartodds.co.uk> Message-ID: I confirmed the admin node reboot (even shutdown) doesn't cause to fail kubectl (I even confirmed while the admin node is down, kubectl still works, and I also checked kubectl conf points to k8s master node), so it must be something related to when the admin node is updated (& subsequently rebooted). I will check more detail next time the admin node is updated and confirm the situation. If you can try, you may also try kubectl soon after you initiated the admin node update (& subsequent auto reboot) in the dashboard during the process.. Regarding the dashboard loading (taking too long), I see something potentially not clean with salt master connection, and I will check further.. Velum::SaltApi::SaltConnectionException (Net::ReadTimeout): Thanks, Jerry On Sat, Jan 13, 2018 at 1:30 PM, Jerry Hwang wrote: > Okay, what you described is also what I expected. > Thanks for the idea. > > Regards, > Jerry > > On Sat, Jan 13, 2018 at 1:23 PM, Liam McCafferty < > Liam.McCafferty at smartodds.co.uk> wrote: > >> I have never noticed this before so I just rebooted my admin node and I >> can confirm I can still communicate via kubectl to the master node. >> >> >> I have also checked my kube config in ~/.kube/config and I can >> see that the cluster server is set to the master server. does >> your kubeconfig point to your master node? Upon checking my admin node I >> see it also that it has the haproxy k8 containers which I believe deal >> with routing to the k8 api. so if your config is pointed to your admin node >> that would make sense that you cant reach the api server. >> >> >> >> Cheers, >> >> >> Liam >> >> >> >> ------------------------------ >> *From:* Jerry Hwang >> *Sent:* 13 January 2018 21:11 >> *To:* Liam McCafferty >> *Cc:* caasp-beta at lists.suse.com >> *Subject:* Re: [caasp-beta] velum troubleshoot >> >> Right, that is also a good point. (I too much focused on the general >> idea :)) >> >> And it seems I can't get to k8s cluster via kubectl (from my local >> machine) during admin node upgrade & reboot, is it expected? >> >> Thanks, >> Jerry >> >> On Sat, Jan 13, 2018 at 1:07 PM, Liam McCafferty < >> Liam.McCafferty at smartodds.co.uk> wrote: >> >>> No Velum runs on standard docker on the caas admin node ( along with a >>> salt master and a mariadb and various other containers ) where as >>> kubernetes only runs on the master and worker nodes. >>> >>> >>> Hope this helps >>> >>> >>> Regards, >>> >>> >>> Liam >>> ------------------------------ >>> *From:* Jerry Hwang >>> *Sent:* 13 January 2018 21:02 >>> *To:* Liam McCafferty >>> *Cc:* caasp-beta at lists.suse.com >>> *Subject:* Re: [caasp-beta] velum troubleshoot >>> >>> Ah right, all run in container on kubernetes. >>> >>> Thanks, >>> Jerry >>> >>> On Sat, Jan 13, 2018 at 12:50 PM, Liam McCafferty < >>> Liam.McCafferty at smartodds.co.uk> wrote: >>> >>>> Hi Jerry, >>>> >>>> >>>> I always put this down to the fact the node has just rebooted, However >>>> if you wish to view the velum logs it runs inside a container on the admin >>>> node you can find this container via using a docker ps command then use a >>>> docker logs command to get the log output for the container. >>>> >>>> >>>> >>>> Regards, >>>> >>>> >>>> Liam >>>> ------------------------------ >>>> *From:* caasp-beta-bounces at lists.suse.com < >>>> caasp-beta-bounces at lists.suse.com> on behalf of Jerry Hwang < >>>> special011 at gmail.com> >>>> *Sent:* 13 January 2018 18:50 >>>> *To:* caasp-beta at lists.suse.com >>>> *Subject:* [caasp-beta] velum troubleshoot >>>> >>>> Hello, >>>> >>>> Does anyone have a general guideline where or how to check velum? >>>> >>>> I always observe this message in the browser after admin node update >>>> (v2) >>>> > We're sorry, but something went wrong. >>>> > If you are the application owner check the logs for more information. >>>> >>>> Eventually I can get back to the admin node (velum), but sometimes it >>>> takes long, and I thought if I have a list to check or monitor, it'd useful. >>>> >>>> And I noticed I can't get to k8s cluster via kubectl (from my local >>>> machine) during admin node upgrade & reboot, is it expected? >>>> >>>> Jerry >>>> >>>> note: this is to look for some general idea or share, not a support >>>> request. >>>> >>>> ______________________________________________________________________ >>>> This email has been scanned by the Symantec Email Security.cloud >>>> service. >>>> For more information please visit http://www.symanteccloud.com >>>> ______________________________________________________________________ >>>> >>>> This e-mail and any files transmitted with it are confidential and may >>>> be legally privileged. If you receive it in error or are not the intended >>>> recipient you must not copy, distribute or take any action in reliance upon >>>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>>> 0077 <+44%2020%207482%200077> and delete the material from your >>>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>>> registered with the Registrar of Companies for England and Wales with >>>> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >>>> Highgate Road, London NW5 1TL >>>> >>>> >>>> ______________________________________________________________________ >>>> This email has been scanned by the Symantec Email Security.cloud >>>> service. >>>> For more information please visit http://www.symanteccloud.com >>>> ______________________________________________________________________ >>>> >>>> This e-mail and any files transmitted with it are confidential and may >>>> be legally privileged. If you receive it in error or are not the intended >>>> recipient you must not copy, distribute or take any action in reliance upon >>>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>>> 0077 <+44%2020%207482%200077> and delete the material from your >>>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>>> registered with the Registrar of Companies for England and Wales with >>>> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >>>> Highgate Road, London NW5 1TL >>>> >>>> >>> >>> >>> ______________________________________________________________________ >>> This email has been scanned by the Symantec Email Security.cloud service. >>> For more information please visit http://www.symanteccloud.com >>> ______________________________________________________________________ >>> >>> This e-mail and any files transmitted with it are confidential and may >>> be legally privileged. If you receive it in error or are not the intended >>> recipient you must not copy, distribute or take any action in reliance upon >>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>> 0077 <+44%2020%207482%200077> and delete the material from your >>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>> registered with the Registrar of Companies for England and Wales with >>> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >>> Highgate Road, London NW5 1TL >>> >>> >>> ______________________________________________________________________ >>> This email has been scanned by the Symantec Email Security.cloud service. >>> For more information please visit http://www.symanteccloud.com >>> ______________________________________________________________________ >>> >>> This e-mail and any files transmitted with it are confidential and may >>> be legally privileged. If you receive it in error or are not the intended >>> recipient you must not copy, distribute or take any action in reliance upon >>> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >>> 0077 <+44%2020%207482%200077> and delete the material from your >>> systems. Smartodds is a business carried on by Smartodds Limited, a company >>> registered with the Registrar of Companies for England and Wales with >>> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >>> Highgate Road, London NW5 1TL >>> >>> >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 540 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> ______________________________________________________________________ >> >> This e-mail and any files transmitted with it are confidential and may be >> legally privileged. If you receive it in error or are not the intended >> recipient you must not copy, distribute or take any action in reliance upon >> it. Instead, please notify us immediately by telephoning +44 (20) 7482 >> 0077 <+44%2020%207482%200077> and delete the material from your systems. >> Smartodds is a business carried on by Smartodds Limited, a company >> registered with the Registrar of Companies for England and Wales with >> number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 >> Highgate Road, London NW5 1TL >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcastelli at suse.com Mon Jan 15 01:35:12 2018 From: fcastelli at suse.com (Flavio Castelli) Date: Mon, 15 Jan 2018 09:35:12 +0100 Subject: [caasp-beta] caas v2 networking In-Reply-To: References:

<538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com>

Message-ID: <81d1b1a3-a0f4-c98d-86bb-34203323d8e9@suse.com> Next major release of SUSE Container as a Service Platform will use flannel deployed as a CNI plugin. We are currently evaluating other networking solutions. Thanks for your suggestion, we will take a look also at kube-router. Cheers Flavio On 01/12/2018 06:29 PM, Jerry Hwang wrote: > Hello, > > Does SUSE have a plan/consideration about kube-router project > (https://github.com/cloudnativelabs/kube-router) vs. CNI vs. flannel? > > Thanks, > Jerry > > On Wed, Dec 20, 2017 at 1:52 PM, Jerry Hwang > wrote: > > Nice, thanks Alvaro for the clarification. > > Jerry > > On Wed, Dec 20, 2017 at 1:38 PM, Alvaro Saurin > > wrote: > > > > 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. > > Cheers > > > Alvaro > > > > > On 12/20/2017 09:05 PM, Jerry Hwang wrote: >> Thanks Flavio. >> So SUSE CaaS v2 networking is flannel (overlay). >> Regardless I set "hostNetwork: True" for Pod, the inter-nodes >> traffic will be still encapsulated in udp backend? >> Any consideration for non-overlay networking solution for v3+? >> >> Jerry >> >> On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli >> > wrote: >> >> On 12/11/2017 05:13 AM, Jerry Hwang wrote: >> > I have a general question. >> > CaaS v2 networking is flannel overlay networking using >> udp encapsulation >> > for traffic between nodes. >> > If my app is based on docker "host" networking >> (net=host), how to make >> > the app migration from docker to caas/kubernetes env >> possible? >> >> You can still tell kubernetes to create a pod that uses >> the host network: >> >> kind: Pod >> spec: >> ? hostNetwork: True >> ... >> >> However please evaluate whether that makes still sense in >> the kubernetes >> context. >> >> Cheers >> Flavio >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta >> >> >> >> >> >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta >> > > -- > Alvaro Saurin > Senior Software Engineer > SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755 ; https://www.suse.com/ > SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) > > > From special011 at gmail.com Mon Jan 15 09:57:01 2018 From: special011 at gmail.com (Jerry Hwang) Date: Mon, 15 Jan 2018 08:57:01 -0800 Subject: [caasp-beta] caas v2 networking In-Reply-To: <81d1b1a3-a0f4-c98d-86bb-34203323d8e9@suse.com> References:

<538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com>

<81d1b1a3-a0f4-c98d-86bb-34203323d8e9@suse.com> Message-ID: 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. Regards, Jerry On Mon, Jan 15, 2018 at 12:35 AM, Flavio Castelli wrote: > Next major release of SUSE Container as a Service Platform will use > flannel deployed as a CNI plugin. > > We are currently evaluating other networking solutions. Thanks for your > suggestion, we will take a look also at kube-router. > > Cheers > Flavio > > On 01/12/2018 06:29 PM, Jerry Hwang wrote: > > Hello, > > > > Does SUSE have a plan/consideration about kube-router project > > (https://github.com/cloudnativelabs/kube-router) vs. CNI vs. flannel? > > > > Thanks, > > Jerry > > > > On Wed, Dec 20, 2017 at 1:52 PM, Jerry Hwang > > wrote: > > > > Nice, thanks Alvaro for the clarification. > > > > Jerry > > > > On Wed, Dec 20, 2017 at 1:38 PM, Alvaro Saurin > > > wrote: > > > > > > > > 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. > > > > Cheers > > > > > > Alvaro > > > > > > > > > > On 12/20/2017 09:05 PM, Jerry Hwang wrote: > >> Thanks Flavio. > >> So SUSE CaaS v2 networking is flannel (overlay). > >> Regardless I set "hostNetwork: True" for Pod, the inter-nodes > >> traffic will be still encapsulated in udp backend? > >> Any consideration for non-overlay networking solution for v3+? > >> > >> Jerry > >> > >> On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli > >> > wrote: > >> > >> On 12/11/2017 05:13 AM, Jerry Hwang wrote: > >> > I have a general question. > >> > CaaS v2 networking is flannel overlay networking using > >> udp encapsulation > >> > for traffic between nodes. > >> > If my app is based on docker "host" networking > >> (net=host), how to make > >> > the app migration from docker to caas/kubernetes env > >> possible? > >> > >> You can still tell kubernetes to create a pod that uses > >> the host network: > >> > >> kind: Pod > >> spec: > >> hostNetwork: True > >> ... > >> > >> However please evaluate whether that makes still sense in > >> the kubernetes > >> context. > >> > >> Cheers > >> Flavio > >> _______________________________________________ > >> caasp-beta mailing list > >> caasp-beta at lists.suse.com > > >> http://lists.suse.com/mailman/listinfo/caasp-beta > >> > >> > >> > >> > >> > >> _______________________________________________ > >> caasp-beta mailing list > >> caasp-beta at lists.suse.com > >> http://lists.suse.com/mailman/listinfo/caasp-beta > >> > > > > -- > > Alvaro Saurin alvaro.saurin at suse.com> > > Senior Software Engineer > > SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: > +49-911-74053-0; Fax: +49-911-7417755 ; > https://www.suse.com/ > > SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham > Norton, HRB 21284 (AG N?rnberg) > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Wed Jan 31 13:21:58 2018 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 31 Jan 2018 12:21:58 -0800 Subject: [caasp-beta] kubernetes components in systemd unit for container Message-ID: Hello, Just for a general question. I see all kubernetes system components (etcd, apiserver, controller, scheduler, kubelet, kube-proxy) run in systemd unit rather than in container in SUSE CaaS v2. Just curious about SUSE's preference/direction and does anyone have an idea/opinion of pros & cons in between the two approaches? Regards, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: