Configurable default backend

[kjoller]

Hello, I am currently experimenting with Xposer running with Træfik as my ingress controller.

However, when I have multiple services defined with expose: "true", I have Traefik acting up, due to the default backend defined in the Xposer-generated ingress. I am flooded with these log messages:

time="2019-03-13T09:40:24Z" level=error msg="Error creating global backend for ingress default/example-apache: duplicate frontend: global-default-frontend"
time="2019-03-13T09:40:24Z" level=error msg="Error creating global backend for ingress default/example-apache: duplicate frontend: global-default-frontend"
time="2019-03-13T09:40:26Z" level=error msg="Error creating global backend for ingress default/example-nginx: duplicate frontend: global-default-frontend"
time="2019-03-13T09:40:26Z" level=error msg="Error creating global backend for ingress default/example-apache: duplicate frontend: global-default-frontend"

The advice in traefik/traefik#4266 is to remove the backend-section directly below spec: in the ingress, thereby changin: this:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  creationTimestamp: "2019-03-13T08:58:45Z"
  generation: 1
  name: example-apache
  namespace: default
  resourceVersion: "947618"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/example-apache
  uid: 351ede0d-456e-11e9-8cd6-c84e578580e0
spec:
  backend:
    serviceName: example-apache
    servicePort: 80
  rules:
  - host: example-apache.default.mydomain.com
    http:
      paths:
      - backend:
          serviceName: example-apache
          servicePort: 80
        path: /
status:
  loadBalancer: {}

into this:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  creationTimestamp: "2019-03-13T08:58:45Z"
  generation: 1
  name: example-apache
  namespace: default
  resourceVersion: "947618"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/example-apache
  uid: 351ede0d-456e-11e9-8cd6-c84e578580e0
spec:
  rules:
  - host: example-apache.default.mydomain.com
    http:
      paths:
      - backend:
          serviceName: example-apache
          servicePort: 80
        path: /
status:
  loadBalancer: {}

Is this possible to do in Xposer, or is there another solution to this problem (other than using nginx as ingress controller)?

[ahsan-storm]

Hello @kjoller, right now we can not remove the backend section directly using Xposer, but it can be done. Do you plan to create a PR for it?

[kjoller]

@ahsan-storm I would like to give it a try, although Go is not my expertise. I would think to add it in the config something like this:

domain: stakater.com
ingressURLTemplate: "{{.Service}}.{{.Namespace}}.{{.Domain}}"
ingressURLPath: /
ingressNameTemplate: "{{.Service}}"
tls: false
defaultBackend: false

Would that, in your opinion be the proper place for it?

I have currently created a private version with the backend section violently ripped out. It seems to work find with both nginx and traefik ingress controllers. I am not sure why it would be needed anywhere, but I am not going to claim deep knowledge in the field.

[rasheedamir]

@kjoller i see you made changes in your fork; i wonder if you would like to make a PR for this change?