kubernetes-ingress
kubernetes-ingress copied to clipboard
HAProxy Kubernetes Ingress Controller
Hello, Is there any intent to support using the caching feature of HAProxy through the kubernetes-ingress ? https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#6 https://www.haproxy.com/documentation/haproxy-configuration-tutorials/network-performance/caching/ Maybe there is some workaround currently using snippets ? Thanks!
I have Ingress with `request-redirect` annotation: ``` ## ... annotations: haproxy.org/request-redirect: www.example.org spec: rules: - host: example.com ## ... ``` When I send request for `https://example.org`, I expect response with...
In TCP service sometime we get client_ip as an internal ip how can we get an external ip in tcp log
I have seen sometime we get external IP and sometime we are getting internal IP. Is that expected?
Using a non-existent ConfigMap `haproxy-controller/haproxy-kubernetes-ingress-wrong`: ``` containers: - name: kubernetes-ingress-controller image: "haproxytech/kubernetes-ingress:1.10.10" imagePullPolicy: IfNotPresent args: - --configmap=haproxy-controller/haproxy-kubernetes-ingress-wrong - --disable-http ``` And the `curl http://:443/myapp` gets the response in clear from...
Hi, i have configured two ingress like this: one subdomain **argocd.domain.tld** with **https** and one ***.domain.tld** with **ssl-passthrough**. With this configuration the haproxy configuration created by operator always give precedence...
would be nice if the ingress would include geoips, including the ability to block regions directly in annotations
Here is my TCP service configmap: ``` apiVersion: v1 kind: ConfigMap metadata: name: smtp-config namespace: ingress-haproxy annotations: argocd.argoproj.io/sync-wave: "-1" data: 587: # Port where the frontend is going to listen...
# For gateway API (≥ v0.5.1) # ## New annotation in TCPRoute ## ```yaml apiVersion: gateway.networking.k8s.io/v1alpha2 kind: TCPRoute metadata: annotations: haproxy.org/send-proxy-v2: 'true' ``` this will enable to use HAProxy v2...
remove deprecated v1alpha2 apis in favor of v1beta1