kubernetes-ingress
kubernetes-ingress copied to clipboard
haproxytech
HAProxy Kubernetes Ingress Controller
In cloud-based Kubernetes environments, it is common to have multiple availability zones within the same cluster. Starting from Kubernetes 1.31, kube-proxy implements a type of load balancing that prioritizes keeping...
This is more of a feature request than an issue. I would like the ability to create a backend using the TCP CRD without requiring a frontend. This would allow...
Today, it's possible to configure a TCP or Backend object to switch between multiple TLS services based on the SNI. It's however a bit awkward to do, and there does...
Hi team, I'm currently using the haproxy kubernetes-ingress to expose an MQTT service via the TCP CRD, using SSL with client certificate verification. Here's a simplified version of my TCP...
Haproxy.cfg is not reloaded when pod IP address changes and standalone-backend annotation is true
We experience a buggy behavior when `haproxy.org/standalone-backeng: "true"`. It is the most probable cause of error. When the pod that is under service is deleted and its replicaset or statefulset...
Splits up the single update function into smaller helper functions and reduces code duplication. Furthermore, it checks whether ssl-offload is correctly enabled.
Hi, there is a high severity vulnerability found in recent haproxytech/kubernetes-ingress images. more details about the [vulnerability](https://github.com/advisories/GHSA-wq9g-9vfc-cfq9): Please update openapi3filter package to latest version where they fix this vulnereability.
HAproxy Ingress Helm chart version: 1.41.0 HAproxy version: v3.0.1 92320eac.dirty Container Image: docker.io/haproxytech/kubernetes-ingress:3.0.1 Summary: if a value of response-set-header annotation has a header value with spaces which is enclosed in...
Changed livenessProbe port from `1042` to `1024` for kubectl deployments. The pod did not listen on port `1042`, so connection for healthcheck was refused and the check failed. Changing it...
**Setup:** - Two instances of hap-ingress (3.1.6/3.1.7) running on debian serving as (redundant) external ingress controllers for k8s. - Identical setup / versions of both instances - Pipeline updating certificates...
