question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

io.l5d.ingress matches to default backends too eagerly

See original GitHub issue

I have an ingress rule in the namespace logging. When I use this configuration it doesn’t trigger however all default ingress rules do trigger:

    namers:
    - kind: io.l5d.k8s
    routers:
    - protocol: http
      identifier:
        - kind: io.l5d.ingress
      servers:
        - port: 80
          ip: 0.0.0.0
      dtab: >-
        /svc => /#/io.l5d.k8s;

If I user this configuration it does trigger:

    namers:
    - kind: io.l5d.k8s
    routers:
    - protocol: http
      identifier:
        - kind: io.l5d.ingress
          namespace: logging
      servers:
        - port: 80
          ip: 0.0.0.0
      dtab: >-
        /svc => /#/io.l5d.k8s;

According to the documentation the second configuration should load ingress from all namespaces (logging and default) however it appears to only load them from default.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mejrancommented, Aug 4, 2017

Yes, copy mistake, fixed now, thanks.

0reactions
mejrancommented, Aug 14, 2017

Yeah, exactly right.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Redirect annotations are ignored on default backend. #8713
What happened: Create an ingress for the default backend like so: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: ...
Read more >
Ingress - Kubernetes
If none of the hosts or paths match the HTTP request in the Ingress objects, the traffic is routed to your default backend....
Read more >
Troubleshooting - NGINX Ingress Controller - Kubernetes
There are many ways to troubleshoot the ingress-controller. ... cafe-ingress Namespace: default Address: 10.0.2.15 Default backend: default-http-backend:80 ...
Read more >
All About the Ingress Resource - Learn Cloud Native
Setting a default backend. In most cases the default backend will be set by the Ingress controller. Some Ingress controllers automatically ...
Read more >
Ingress traffic | Linkerd
Traefik should be meshed with ingress mode enabled, i.e. with the linkerd.io/inject: ingress annotation rather than the default enabled . Instructions differ ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found