g time to test and report your findings!
>
> On 08/11/2017 11:10 AM, Baptiste Assmann wrote:
> >
> > Hi All
> >
> > So, I enabled latest (brilliant) contribution from Olivier into my
> > Kubernetes cluster and I discovered it did not work as expected.
> > Af
Hi Aleksandar,
Thanks for your feedback.
> > In one line, we can enable automatic "scalling follow-up" in
> > HAProxy.
> ... for headless services only, right.
Well I think I've already seen my Kubernetes friend distributing IPs
even for nodePort deployments.
> 8-O. I don't say the word amazing
I have a headless service called 'red' in my kubernetes, it
points to my 'red' application)
backend red
server-template red 20 _http._tcp.red.default.svc.cluster.local:8080
inter 1s resolvers kube check
In one line, we can enable automatic "scalling follow-up&
Baptiste
--
---
Baptiste Assmann
Product Manager - Consultant
e: bassm...@haproxy.com| t: https://twitter.com/haproxy_tech
w: http://www.haproxy.com/ | b: http://blog.haproxy.com/
Well your client did not sent the request in less than 10s so haproxy shut the
connection
Cf option http-request 1
cheers
Le 4 avr. 2012 à 18:24, Alon M a écrit :
> sorry forgot to add our config file :
>
> global
>log 127.0.0.1 local0
>chroot /var/lib/haproxy
>
euh forget about the dirty trick, it will print both server name :)
Le 10 nov. 2011 à 19:52, Baptiste a écrit :
> There might be a dirty way:
>
> In your backend, give a try to the above:
>
>
> acl server1 srv_id 1
> acl server2 srv_id 2
> rspadd X-Server:\ server1 if server1
> rs
6 matches
Mail list logo
