Haproxy - make looking for backends only for namespace where deployed.

[maven1987]

Hi, I have a issue with controller.
In my cluster many apps have own backend created by devs and configured thru ingress just like this below:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: apache-airflow
  annotations:
  labels:
    {}
  namespace: airflow
spec:
  **defaultBackend:
    service:
      name: airflow-api-server
      port:
        number: 8080**
  ingressClassName: haproxy
  rules:
    - host: apache-airflow-dev.example.com
      http:
        paths:
          - backend:
              service:
                name: airflow-api-server
                port:
                  number: 8080
            path: /
            pathType: Prefix
  tls:
    - hosts:
        - apache-airflow-dev.example.com
  backend:
    {}

When bolded section is configured and haproxy start it take it as its own default backend for all apps but I don't want it.

Is there option to make haproxy ingress controller to not look for this config in other other namespace or ignore this config section.

For now if controller set it and no rules matches, controller redirect user trafic to this page instead my custom error page configured.
Removing this section from all ingresses is idea but my dev require them.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ivanmatmati]

Hi @maven1987 , thanks for reporting, I see a few things that we need to discuss in the team concerning this default backend and error pages. To answer your question, unfortunately at this time, we implement the default backend at frontend level without any possible restriction or customization.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[joachimbuechse]

A relatively simple fix might be to give precedence to the command line option --default-backend-service (if I'm not mistaken it is currently only used as a fallback).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.