We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using ingress 3.0.1, we're seeing constant reloads with this message
2024-09-03T16:21:11.086417412-04:00 stderr F 2024/09/03 20:21:11 INFO service/service.go:157 [transactionID=f6269b17-dde8-436d-ac00-b740858bfcb9] reload required : Service 'clark-developer-featbit/featbit-dev2-els': backend 'clark-developer-featbit_featbit-dev2-els_80' updated: map[HTTPConnectionMode:[ http-server-close]]
We do have a backend object object
--- apiVersion: "ingress.v1.haproxy.org/v1" kind: Backend metadata: name: featbit-haproxy-backend-config namespace: clark-developer-featbit spec: config: name: featbit-haproxy-backend-config http-server-close: "enabled" tunnel_timeout: 3600000 ...
Ingress object
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: haproxy.org/cr-backend: clark-developer-featbit/featbit-haproxy-backend-config healthcheck: /health/liveness meta.helm.sh/release-name: featbit-dev2 meta.helm.sh/release-namespace: clark-developer-featbit creationTimestamp: "2023-09-29T15:46:58Z" generation: 2 labels: app.kubernetes.io/instance: featbit-dev2 app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: featbit-dev2 argocd.argoproj.io/instance: featbit-dev2 helm.sh/chart: featbit-0.4.1 name: featbit-dev2-els-ingress namespace: clark-developer-featbit resourceVersion: "376035891" uid: d96c0bfc-bc4e-4629-acd6-2e300e42c41a spec: ingressClassName: haproxy rules: - host: featbit-eval-2.dev.internal http: paths: - backend: service: name: featbit-dev2-els port: number: 80 path: / pathType: ImplementationSpecific
The text was updated successfully, but these errors were encountered:
Thanks @tman5 for reporting, We've seen this bug and will provide a fix.
Sorry, something went wrong.
ivanmatmati
No branches or pull requests
Using ingress 3.0.1, we're seeing constant reloads with this message
We do have a backend object object
Ingress object
The text was updated successfully, but these errors were encountered: