Ingress-nginx: nginx ingress always returns 404

[bzolivereckle]

Setup the Ingress controller like described here with small changes.

https://docs.microsoft.com/de-de/azure/aks/ingress-tls

also running a keycloak with its ingress.

{
  "kind": "Ingress",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "keycloak",
    "namespace": "idp",
    "selfLink": "/apis/extensions/v1beta1/namespaces/idp/ingresses/keycloak",
    "uid": "88418a99-e924-11e9-a4e0-860475bde06a",
    "resourceVersion": "836388",
    "generation": 3,
    "creationTimestamp": "2019-10-07T17:04:32Z",
    "labels": {
      "app.kubernetes.io/instance": "keycloak",
      "app.kubernetes.io/managed-by": "Tiller",
      "app.kubernetes.io/name": "keycloak",
      "helm.sh/chart": "keycloak-5.1.7"
    },
    "annotations": {
      "certmanager.k8s.io/cluster-issuer": "letsencrypt-prod",
      "kubernetes.io/ingress.class": "nginx"
    }
  },
  "spec": {
    "tls": [
      {
        "hosts": [
          "<<myhost>>"
        ],
        "secretName": "tls-secret"
      }
    ],
    "rules": [
      {
        "host": "<<myhost>>",
        "http": {
          "paths": [
            {
              "path": "/auth/?(.*)",
              "backend": {
                "serviceName": "keycloak-http",
                "servicePort": "http"
              }
            }
          ]
        }
      }
    ]
  },
  "status": {
    "loadBalancer": {
      "ingress": [
        {}
      ]
    }
  }
}

Logs from nginx:

I1008 10:09:04.695353 6 event.go:255] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"idp", Name:"keycloak", UID:"88418a99-e924-11e9-a4e0-860475bde06a", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"836388", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress idp/keycloak
I1008 10:09:04.695841 6 controller.go:134] Configuration changes detected, backend reload required.
I1008 10:09:04.767039 6 controller.go:150] Backend successfully reloaded.
10.240.0.4 - - [08/Oct/2019:10:09:10 +0000] "GET /auth HTTP/2.0" 404 21 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0" 356 0.002 [upstream-default-backend] [] 10.244.0.14:8080 21 0.004 404 d2f7be504895758657d0c8767855bb10
10.240.0.4 - - [08/Oct/2019:10:09:10 +0000] "GET /favicon.ico HTTP/2.0" 404 21 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0" 38 0.001 [upstream-default-backend] [] 10.244.0.14:8080 21 0.000 404 53b094262de55f25e127589ad5792874

no errors nothing but still get default 404 page.

What i already checked:

• service is in the same namespace like the ingress
• SSL Certificate from tls-secret has correct SAN
• also recreate the whole setup several times to avoid some mistakes.

But still not working. Any idea how to investigate?
Thx

[StanleyShen]

I have similar issue when setting it on aws environment, when accessing service, I always get 404 as well, no error as well.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.