Skip to main content

Ingress

Not availableCloud AvailableSelf-Managed Community (OSS)AvailableSelf-Managed Enterprise
tip

If you are using abctl to manage your deployment, a nginx ingress is automatically provided for you. There is no need to provision an additional ingress.

To access the Airbyte UI, you will need to manually attach an ingress configuration to your deployment. These guides assume that you have already deployed an Ingress Controller. The following is a simplified definition of an ingress resource you could use for your Airbyte instance:

If you don't already have an NGINX controller installed, you can do it by running helm install my-release oci://ghcr.io/nginxinc/charts/nginx-ingress --version 1.3.1 or following the instructions from NGINX.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: airbyte-ingress # ingress name, example: airbyte-production-ingress
annotations:
ingress.kubernetes.io/ssl-redirect: "false"
spec:
ingressClassName: nginx
rules:
- host: localhost # host, example: airbyte.company.example
http:
paths:
- backend:
service:
# format is ${RELEASE_NAME}-airbyte-webapp-svc
name: airbyte-airbyte-webapp-svc
port:
number: 80 # service port, example: 8080
path: /
pathType: Prefix
- backend:
service:
# format is ${RELEASE_NAME}-airbyte-keycloak-svc
name: airbyte-airbyte-keycloak-svc
port:
number: 8180
path: /auth
pathType: Prefix
- backend:
service:
# format is ${RELEASE_NAME}-airbyte--server-svc
name: airbyte-airbyte-server-svc
port:
number: 8001
path: /api/public
pathType: Prefix