Arnaud C

Hi again :) , So I now have working (but quite disgusting code). I think about two things: - Separate parsing and printing in two distinct modules (one for ultralight...

So I have started investigating how it could work. Proxy protocol is supposed to be activated through the `PROXY_PROTOCOL` env variable, which i have set in the extraEnvVars of the...

Well, I got it working with the following extraEnvVars: ``` extraEnvVars: - name: PROXY_PROTOCOL value: "mail" - name: REAL_IP_FROM value: "10.42.0.0/16,fd23:23:42:0::/56" ``` The service now listens both on IPV4 and...

Hi again :-) I came across an issue on my dual stack (IPv4 + IPv6) deployment. It looks like Dovecot is not happy when Proxy Protocol specifies and IPv6 address...

The referenced PR has the side effect that the variables that are modified in the kubeadm-config file are not reflected in the manifests anymore. Example: modify the kube_scheduler_bind variable in...

@tmurakam Well I'm fiddling with our cluster right now. It seems that the kubeadm upgrade command was not meant to reconfigure the cluster, my bad. To apply the changes to...

I just setup the same workaround as @dlford. It makes no sense to make use of proxy-protocol for https, and it would also not fix the initial issue.