Skip to content

abctl v0.30.1 installs Airbyte v1.8.1 with incorrect ingress target (webapp-svc instead of server-svc) #65539

@YChanHuang

Description

@YChanHuang

What happened?

Ingress misconfigured to non-existent webapp-svc, causing Airbyte UI/API HTTP 503 errors

After installing Airbyte with abctl, the generated ingress is misconfigured. It points to airbyte-abctl-airbyte-webapp-svc, but that service is not created in the deployment. As a result, the ingress cannot route traffic correctly, and access to the Airbyte UI/API fails with a service not found error and returns HTTP 503 Service Unavailable.

This happens both in local and EC2 installations, and requires manual intervention (editing the ingress to use airbyte-abctl-airbyte-server-svc) to restore functionality.

Additional info / Steps to reproduce:

Install Airbyte:

abctl local install --airbyte-version 1.8.1

Check ingress:

kubectl describe ingress ingress-abctl -n airbyte-abctl

Error: services "airbyte-abctl-airbyte-webapp-svc" not found

What did you expect to happen?

The ingress should be generated with the correct service target (**airbyte-abctl-airbyte-server-svc**) so that the Airbyte UI and API are accessible immediately after installation, without requiring any manual edits.

I've attempted to provide the ingress config through values.yaml.

ingress:
  enabled: true
  className: nginx
  annotations:
    kubernetes.io/ingress.class: nginx
  hosts:
    - host: localhost
      paths:
        - path: /api/v1/connector_builder
          pathType: Prefix
          backend:
            service:
            name: airbyte-abctl-airbyte-connector-builder-server-svc
            port: http
        - path: /
          pathType: Prefix
          backend:
            service:
              name: airbyte-abctl-airbyte-server-svc
              # port:
              #   number: 8000
              port: http

…but the ingress still defaults to airbyte-abctl-airbyte-webapp-svc instead of airbyte-abctl-airbyte-server-svc.

Abctl Version

I have tried below versions v0.28.0 v0.29.0 v0.30.1

Docker Version

On Linux (EC2)

Server: Docker Engine - Community
Engine:
Version: 28.3.3
API version: 1.51 (minimum version 1.24)
Go version: go1.24.5
Git commit: bea959c
Built: Fri Jul 25 11:34:00 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0

On mac

Server: Docker Engine - Community
Engine:
Version: 28.3.3
API version: 1.51 (minimum version 1.24)
Go version: go1.24.5
Git commit: bea959c
Built: Fri Jul 25 11:34:22 2025
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v2.1.4
GitCommit: 75cb2b7193e4e490e9fbdc236c0e811ccaba3376
runc:
Version: 1.3.0
GitCommit: 4ca628d1d4c974f92d24daccb901aa078aad748e
docker-init:
Version: 0.19.0
GitCommit: de40ad0

OS Version

# On Linux (EC2):
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

# On Mac:
$ uname -a
Darwin Kernel Version 24.6.0: ;RELEASE_ARM64_T6041 arm6

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions