Issue with Airbyte API server connection through Kubernetes Ingress

Summary

The user is facing a 503 error and connection timeout when trying to access the Airbyte API server through Kubernetes Ingress with Nginx. The provided Ingress file points to different ports for the services, but the connection is failing.


Question

Hello folks, I’m trying to use the airbyte-api-server under port 8006, my airbyte is deployed on kubernetes and running under a nginx ingress. I created an ingress file pointed the airbyte-airbyte-server-svc and airbyte-airbyte-api-server-svc to the same url, but in diferent port.
But when I try call to api they return error 503 and sometime this message: curl: (28) Failed to connect to http://airbyte.xxxx.sslip.io|airbyte.xxxx.sslip.io port 8006 after 130526 ms: Couldn’t connect to server.
Is someone already saw this issue or can help us on this?

Below is the ingress file that I use:
<@U06SV3WK399>

kind: Ingress
metadata:
  name: airbyte-ingress
  annotations:
    <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
    <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-prod
spec:
  tls:
    - hosts:
        - <http://airbyte.xxx.sslip.io|airbyte.xxx.sslip.io>     
      secretName: airbyte-tls
  rules:
    - host: <http://airbyte.xxx.sslip.io|airbyte.xxx.sslip.io>  
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: airbyte-airbyte-webapp-svc
                port:
                  number: 80
          - path: /v1
            pathType: Prefix
            backend:
              service:
                name: airbyte-airbyte-api-server-svc
                port:
                  number: 8006```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1712930890375849) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte-api-server", "kubernetes", "nginx-ingress", "503-error", "connection-timeout"]
</sub>

For us we had to configure the services as nodeport

    service:
      type: NodePort```

We are not using nginx ingress though. We are using the AWS Load Balancer Controller

The services are clusterip by default

Tks <@U064R6L3ZBJ> I’ll check about to put this as nodeport