The ins and outs of networking in Google Container Engine and Kubernetes (Google Cloud Next '17)

[@ch4.hayabusa]

16:35 appreciate the honesty... This is such a massive code as infrastructure library with a billion plugins... There is a steep learning curve

[@mangeshbharsakle5847]

Awesome. Networking is Deep and Complex

[@sampowers1234]

this talk is so good. I like the repitition (reinforcement).

[@dineshdeshmukh2801]

Must watch for beginners...no docs or blogs can match this.

[@cla2008]

doesnt make any sense. blog with the same information would be a lot better, since you can search text\you can skip parts you know\etc. videos are by far the worst medium to pass information so far.

[@ajit555db]

wow, jewel of a presentation to understand k8s networking.

[@danielhd6719]

First understand how networking overall works (without custom implementations on k8s) and you will understand anything that will be created in the next 50 years..

[@tomviglini]

Very informative!

[@jacekszlachta5339]

Awesome presentation!

[@user-kf8ez2uz7d]

For the DNAT approach, when the load balancer forwards the request patch to the VM node, it does not change the destination IP and port, so, it means the load balancer and the VM node should be in the same L2 network, right?

[@gaatutube]

Great talk. Thanks.

[@zhq527725]

Thanks, very cool talk! And you guys are humorous :-)

[@ajit555db]

The big downside of using the Network LB for ingress is that each service you expose with a LoadBalancer will get its own IP address, and you have to pay for a LoadBalancer per exposed service, which can get expensive!

[@danielhd6719]

Thats why you create an ingress in such a case and split traffic between services using path

[@zhigangqiu9380]

Where can download the slides?

[@jianjunxie7236]

speakerdeck.com/thockin/the-ins-and-outs-of-networking-in-google-container-engine

[@shadyshandilya]

@@jianjunxie7236 thanks

[@adampinuelas6139]

4