charts
charts copied to clipboard
haproxy-ingress
HAProxy Ingress helm charts
IPv6 only, HAProxy `/healthzPort` is listening to port 10254. Where this port comes from is bit unclear. Also the configuration uses in readiness probe config uses `:10254` instead of `[::]:10254`
Hi @jcmoraisjr , How can I change the port here for lb-tcp-80 and lb-tcp-443? The reason I want to change them because I have another nginx running in my kube-system...
I am using this ingress controller in a manner similar to #23. I'm using `controller.hostNetwork=true` and thus do not require the `Service` resource that this chart creates. My values config...
The image for the default-backend defaults to `k8s.gcr.io/defaultbackend-amd64` in the helm chart, which naturally fails when deploying on arm64. It would be nice to have it point to a manifest...
Hello guys - Just curious if there is a reason to maintain both of these charts? https://github.com/haproxytech/kubernetes-ingress Cheers 😄
Hi Guys I've enabled sidecar logging `controller.logs.enabled: true` but in the request logs I see the IP address of the haproxy ingress pod (10.42.3.133 in my case) and not the...
Hi! I'm using Fluxv2 to deploy haproxy-ingress chart to my cluster. I've noticed that each time I change values that are destined for ConfigMap I have ingress controller pods recreated....
In a dual-stack (or IPv6 only) cluster, `localhost` resolves to `::1`. HAProxy is configured to log to `localhost:514` and dutifully sends log messages to `[::1]:514`, but the `whereisaaron/kube-syslog-sidecar` listens only...
https://github.com/kubernetes/kubernetes/pull/97171 >The PodSecurityPolicy API is deprecated in 1.21, and will no longer be served starting in 1.25. For some cloudvendors this timeline is even more strict. like azure AKS. most...
Hello and thanks for your work on this ingress controller. We tested with many different settings but we keep getting the following error: * installation `helm upgrade --install -n haproxy-ingress...
