Thanks to visit codestin.com
Credit goes to github.com

Skip to content

io.l5d.ingress matches to default backends too eagerly #1566

@mejran

Description

@mejran

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions