Ingress settings with Nebari helm extension are not working

[konkapv]

OS system and architecture in which you are running QHub

Linux

Expected behavior

I am trying to setup Airflow through Nebari helm extension. I am able to set it up, I could verify it running with port forward to localhost. I am trying to make it available on our domain, so I setup following ingress route and middleware. When I try to access the URL, I could see the request in the Airflow webserver log, but returning 404 error. Expected result is to return Http 200 OK

Actual behavior

Getting 404 error

How to Reproduce the problem?

Please see the attached qhub-config.yml, ingress.yml, middleware.yml to reproduce the issue on Linux env.

airflow-ingress.zip

Command output

No response

Versions and dependencies used.

conda = 4.12.0 Qhub = 0.4.3 kubectl Client Version: v1.24.4 Kustomize Version: v4.5.4

Compute environment

AWS

Integrations

No response

Anything else?

No response

[viniciusdc]

Hi @konkapv could you post the error msg output (GET) from the api server?

[konkapv]

@viniciusdc

• Connected to mss-onyx-dev.metrostar.cloud (100.20.133.58) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
• ALPN, server accepted to use h2
• Server certificate:
• subject: CN=TRAEFIK DEFAULT CERT
• start date: Oct 3 20:15:25 2022 GMT
• expire date: Oct 3 20:15:25 2023 GMT
• issuer: CN=TRAEFIK DEFAULT CERT
• SSL certificate verify result: self signed certificate (18), continuing anyway.
• Using HTTP2, server supports multiplexing
• Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
• h2h3 [:method: HEAD]
• h2h3 [:path: /airflow/]
• h2h3 [:scheme: https]
• h2h3 [:authority: mss-onyx-dev.metrostar.cloud]
• h2h3 [user-agent: curl/7.82.0]
• h2h3 [accept: /]
• Using Stream ID: 1 (easy handle 0x7fffd4d0be90)

HEAD /airflow/ HTTP/2 Host: mss-onyx-dev.metrostar.cloud user-agent: curl/7.82.0 accept: /

• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• Connection state changed (MAX_CONCURRENT_STREAMS == 250)! < HTTP/2 404 HTTP/2 404 < content-type: text/plain; charset=utf-8 content-type: text/plain; charset=utf-8 < x-content-type-options: nosniff x-content-type-options: nosniff < content-length: 19 content-length: 19 < date: Mon, 03 Oct 2022 20:17:12 GMT date: Mon, 03 Oct 2022 20:17:12 GMT

<

• Connection #0 to host mss-onyx-dev.metrostar.cloud left intact

[viniciusdc]

Thanks, @konkapv. I will try to replicate this here and will follow back after some debugging. c.c. @iameskild for visibility as well

[iameskild]

We will need to try and recreate this issue and then we can follow up.

[dcmcand]

Closing as a stale issue. Please reopen if the issue recurs.