I am writing a wrapper that connects with RemoteRuntimeService which
Kubelet uses to communicate with dockershim.sock. I was under the
impression that calling remote.NewRemoteRuntimeService with
"unix:///var/run/dockershim.sock" will make a Grpc client connection from
my wrapper go through
Point of clarity - not necessarily L2. Flat L3 space is closer.
On Fri, Mar 9, 2018, 4:46 PM Igor Cicimov
wrote:
> In kubernetes ALL pods have access to each other by default they reside in
> a flat L2 lan space.
>
> --
> You received this message because you
On Tuesday, August 8, 2017 at 6:56:33 PM UTC+8, Mehdy Bohlool wrote:
> This is a little old, but you can also take a look at our client python,
> specifically this example:
> https://github.com/kubernetes-incubator/client-python/blob/master/examples/exec.py
>
> On Tuesday, February 28, 2017 at
I suggest you peruse Mark’s excellent blog post (series) where in part
1 he answers your question and more in great detail:
https://medium.com/google-cloud/understanding-kubernetes-networking-pods-7117dd28727
Cheers,
Michael
--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/