Port : http inside IngressRoute => block all IngressRoute

Traefik Traefik v2 (latest)
1

Unlucky someone on my team has set port: http inside IngressRoute (see at the end) in result I've got all IngressController pod with this kind of error:

E0331 12:48:03.608768 1 reflector.go:125] pkg/mod/k8s.io/client-go@v0.0.0-20190718183610-8e956561bbf5/tools/cache/reflector.go:98: Failed to list *v1alpha1.IngressRoute: v1alpha1.IngressRouteList.Items: []v1alpha1.IngressRoute: v1alpha1.IngressRoute.v1alpha1.IngressRoute.Spec: v1alpha1.IngressRouteSpec.Routes: []v1alpha1.Route: v1alpha1.Route.Services: []v1alpha1.Service: v1alpha1.Service.LoadBalancerSpec: Port: readUint32: unexpected character: �, error found in #1 byte of ...|http|..., bigger context ...|http|...

and so on doesn't serve any route.
I agree it's an error of conf but the result impact all K8S ingress route so on all exposed applications.

- apiVersion: traefik.containo.us/v1alpha1
  kind: IngressRoute
  metadata:
    annotations:
    creationTimestamp: "2020-03-25T20:41:10Z"
    generation: 1
    name: s-10472e71-6256-411c-a342-291f97bf0336-squid-ingressroute
    namespace: s-10472e71-6256-411c-a342-291f97bf0336
  spec:
    entryPoints:
    - web
    routes:
    - kind: Rule
      match: Host(`squid-10472e71-6256-411c-a342-291f97bf0336.k8s-serv.nd-int-ops-paas.itn.intraorange`)
        && PathPrefix(`/`)
      services:
      - kind: Service
        name: squid
        namespace: s-10472e71-6256-411c-a342-291f97bf0336
        port: http
2

Thanks @obeyler, just saw that you have created an issue https://github.com/containous/traefik/issues/6614

3

Yes I've done it :wink:

4

Hi

Has this issue been fixed?

Thanks!

Dian

5

Yes they've done.
But I don't make mistake on my Ingressroute anymore so I can't say if the CRD with more control are enough to evict all error