Hi Conrad,
> first of all: great to see that this is making progress! I am very
> excited
> about everything related to SRV records and also server-templates. I
> tested
> a fresh master build with these patches applied, here are my
> observations:
Thanks a lot for taking time to test and
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
On 08/11/2017 02:56 PM, Conrad Hoffmann wrote:
> Hi,
>
> first of all: great to see that this is making progress! I am very excited
> about everything related to SRV records and also server-templates. I tested
> a fresh master build with these patches applied, here are my observations:
>
> On
Hi,
first of all: great to see that this is making progress! I am very excited
about everything related to SRV records and also server-templates. I tested
a fresh master build with these patches applied, here are my observations:
On 08/11/2017 11:10 AM, Baptiste Assmann wrote:
> Hi All
>
> So,
Hi Baptiste,
Baptiste Assmann wrote on 11.08.2017:
> Hi All
> So, I enabled latest (brilliant) contribution from Olivier into my
> Kubernetes cluster and I discovered it did not work as expected.
> After digging into the issues, I found 3 bugs directly related to the
> way SRV records must be
Hi Manu,
On Fri, Aug 11, 2017 at 11:31:05AM +0200, Emmanuel Hocdet wrote:
> Hi Christopher, Willy
>
> SSL_CTX_get0_privatekey in openssl-compat.h canât work because internal
> structure usage.
> Christopher, your original workaround is the only way i see.
> Patch to fix that:
Ah cool, thank
Hi Christopher, Willy
SSL_CTX_get0_privatekey in openssl-compat.h can’t work because internal
structure usage.
Christopher, your original workaround is the only way i see.
Patch to fix that:
++
Manu
0001-BUILD-ssl-replace-SSL_CTX_get0_privatekey-for-openss.patch
Description: Binary data
Hi All
So, I enabled latest (brilliant) contribution from Olivier into my
Kubernetes cluster and I discovered it did not work as expected.
After digging into the issues, I found 3 bugs directly related to the
way SRV records must be read and processed by HAProxy.
It was clearly hard to spot them
8 matches
Mail list logo