@kapa.ai We are upgrading airbyte install in kubernetes from chart 1.6.0 to chart 2.0.19 and the helm install is reporting this error:

Helm upgrade failed for release airbyte/airbyte with chart airbyte@2.0.19:
      failed to create resource: admission webhook "<http://validate.nginx.ingress.kubernetes.io|validate.nginx.ingress.kubernetes.io>"
      denied the request: host "<http://airbyte.gke-sydney-test.nonprod.xyz.apnic.net|airbyte.gke-sydney-test.nonprod.xyz.apnic.net>" and
      path "/" is already defined in ingress airbyte/airbyte-webapp

Any thoughts on how to fix this?

The error means your NGINX admission webhook is rejecting the new Ingress from the v2 chart because there is already an Ingress with the same host/path (

airbyte-webapp

) in the cluster. In chart v2, ingress is managed via the new

ingress

block, and the old

webapp

-based ingress from v1 is no longer used. [[Ingress option 1](https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart); [Ingress 1.7+](https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress-1-7)] To fix the conflict: 1. Delete the old v1 ingress (the one named

airbyte-webapp

in the

airbyte

namespace):

bash    kubectl delete ingress airbyte-webapp -n airbyte

(Adjust namespace/name if different.) 2. Ensure you’re using the v2 ingress config in your

values.yaml

(or disable it if you’re bringing your own): - If you want Helm to manage ingress (recommended):

yaml      ingress:        enabled: true        className: "nginx"        hosts:          - host: <http://airbyte.gke-sydney-test.nonprod.xyz.apnic.net|airbyte.gke-sydney-test.nonprod.xyz.apnic.net>            paths:              - path: /                pathType: Prefix                backend: server              - path: /connector-builder                pathType: Prefix                backend: connector-builder-server

[[Ingress option 1](https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress#option-1-use-airbytes-helm-chart)] - If you prefer to manage ingress yourself, disable Helm’s ingress and keep only your own:

yaml      ingress:        enabled: false

[[Bring your own ingress](https://docs.airbyte.com/platform/2.0/deploying-airbyte/integrations/ingress#option-2-bring-your-own-ingress)] 3. Re-run the upgrade:

bash    helm upgrade airbyte airbyte-v2/airbyte \      --namespace airbyte \      --values ./values.yaml \      --version 2.0.19

If you still see the same error, double‑check with

kubectl get ingress -A | grep <http://airbyte.gke-sydney-test.nonprod.xyz.apnic.net|airbyte.gke-sydney-test.nonprod.xyz.apnic.net>

that there is only one Ingress using that host/path before running

helm upgrade

again.