Traefik ingress - transport issue

Traefik Traefik v2 (latest)
1

Hi,

I'm running Traefik on an AKS cluster, using ingressClassName: traefik to tell Traefik that it should be used.

Traefik is deployed via Helm, with a http -> https redirect. I have a ingress that looks like this:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: appname
  namespace: "appns"
  annotations:
    traefik.ingress.kubernetes.io/router.tls: "true"
  labels:
    app: appname      
spec:
  ingressClassName: traefik
  rules:  
  - host: someappurl.example-com
    http:
      paths:
      - path: "/"
        pathType: Prefix
        backend:
          service:
            name: appname
            port:
              number: 80

This is published on an internal IP, with a valid certificate. When I am trying to reach the ingress from within the vnet I get the http -> https redirect, but after that it stops. Wget looks like this:

root@somepod-66669dcfff-jg6vm:/app# wget someappurl.example-com
--2022-11-07 14:10:00--  http://someappurl.example-com/
Resolving someappurl.example-com (someappurl.example-com)... 10.0.0.150
Connecting to someappurl.example-com (someappurl.example-com)|10.0.0.150|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://someappurl.example-com/ [following]
--2022-11-07 14:10:00--  https://someappurl.example-com/
Connecting to someappurl.example-com (someappurl.example-com)|10.0.0.150|:443... connected.
HTTP request sent, awaiting response...

Any suggestions on what to look for here? In the Traefik dashboard it looks alright with the router, service, and middleware all showing with a green checkmark. If I proxy directly to the service it works (I.e bypassing Traefik)

2

The mistake here was simple:

Thought namespace exclusion in a network policy was enough, but needed to allow cluster CIDR aswell

3

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.