On Tue, May 16, 2017 at 11:14 AM, Joe Auty wrote:
> Thanks again Tim!
>
> What would a recommended architecture look like for a socket.io sort of
> setup?
I don't know socket.io per se, but I can speak abstractly...
> Needs:
>
> - session affinity (I think either L4 or 7!?) FWIW the provided soc
On Tue, May 16, 2017 at 11:08 AM, Joe Auty wrote:
> The only real choice there is "ClientIP", which makes sense in an L4
> context.
>
>
> But wouldn't the IP need to be forwarded as an HTTP header? How does it know
> what the IP is?
When you use an L7 frontend like GCLB and an L4 Service, it will
On Tuesday, May 16, 2017, wrote:
> I have a stand-alone kubelet running with no api server. Essentially
> using it to more easily manage the docker daemon on a single host and do
> not want to set up the API server.
>
> Is there a way to put kubectl in like a "stand-alone" mode? Main things I
>
You're invited to a free webinar to learn how to build neural
nets for deep learning and use other highly automated machine
learning functionalities with the Wolfram Language.
You'll learn about
* the neural net framework
* symbolically building and training your own neural nets
* putting pr
>
> Essentially using it to more easily manage the docker daemon on a single
> host
>
Can you explain how is managing docker daemon on a single host difficult
for you?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes user discussion and Q&A" group.
I have a stand-alone kubelet running with no api server. Essentially using it
to more easily manage the docker daemon on a single host and do not want to set
up the API server.
Is there a way to put kubectl in like a "stand-alone" mode? Main things I want
to be able to do is list pods, exec i
Thanks again Tim!
What would a recommended architecture look like for a socket.io sort of
setup?
Needs:
- session affinity (I think either L4 or 7!?) FWIW the provided
socket.io examples are for HAProxy and NGinx
- if we use HAProxy/NGinx, redundancy of these services would be great
- LB is
The only real choice there is "ClientIP", which makes sense in an L4 context.
But wouldn't the IP need to be forwarded as an HTTP header? How does it
know what the IP is?
Thanks for these great posts, these concepts are really starting to
click now!
'Tim Hockin' via Kubernetes user discuss
On Tue, May 16, 2017 at 7:06 AM, Joe Auty wrote:
> Hi Tim,
>
> I have a couple of different use cases actually, but at this point I'm just
> trying to understand the architecture to know where my LB fits. Options:
>
> - haproxy/nginx outside of the cluster pointing to NodePort/LoadBalancer
> ports
On Tue, May 16, 2017 at 7:02 AM, Joe Auty wrote:
> This is very helpful, thanks, this makes sense!
>
> If services are layer 4 though, what does service.spec.sessionAffinity do?
The only real choice there is "ClientIP", which makes sense in an L4 context.
> If I'm understanding you, NGinx and HA
On Monday, May 15, 2017 at 3:37:26 PM UTC-6, Ahmet Alp Balkan wrote:
> Interesting, I've been able to change the image to busybox from your manifest
> and deploy it as is, and the pod came up.
>
>
> On Mon, May 15, 2017 at 2:13 PM, wrote:
> Here it is with both labels:
>
> thanks
>
>
>
>
Hi Tim,
I have a couple of different use cases actually, but at this point I'm
just trying to understand the architecture to know where my LB fits.
Options:
- haproxy/nginx outside of the cluster pointing to NodePort/LoadBalancer
ports
- haproxy/nginx inside the cluster
- Using just the Goo
This is very helpful, thanks, this makes sense!
If services are layer 4 though, what does service.spec.sessionAffinity do?
If I'm understanding you, NGinx and HAProxy become useful things inside
the cluster to provide layer 7 LB, whereas otherwise a more
application/pod specific perspective (i
13 matches
Mail list logo
