For those experiencing authentication issues with the Connector Builder in 1.7, please see the fix and details here: https://docs.airbyte.com/release_notes/v-1.7#171. There is some further discussion in GitHub about this. See https://github.com/airbytehq/airbyte/issues/61677#issuecomment-3046489964.

This requires some translation if you're on Google Cloud Platform (GCP) and using the Ingress/Classic Load Balancer pattern on GKE (Standard or Autopilot). At least it did for me. Our cluster is on GKE Autopilot (Airbyte is deployed via helm) and historically our Classic Load Balancer backend config has pointed to the `airbyte-webapp`—while this has worked across many Airbyte upgrades, I opted to update to it to

airbyte-server

for consistency with the above solution. However, these are steps I was able to use to get Connector Builder working again: 1. Edit the Service for

airbyte-airbyte-connector-builder-server-svc

and add an annotation of

<http://cloud.google.com/neg|cloud.google.com/neg>: '{"ingress": true}'

(this creates an NEG and allows it to be used in ingress rules) 2. Do the same for the

airbyte-airbyte-server-svc

Service (if you haven't already) 3. Edit the existing Ingress object to add the additional backend and its rules (under

spec.rules[].http.paths[]

) 4. Make sure that the attached Classic Load Balancer actually loads the backends and path mappings correctly. In my case, I got an additional NEG-based backend (probably because of my change from

webapp

) so I needed to update the config a bit to get it back in order That seems to be working for me, so hopefully it'll help others with similar setups. (Initially I had some trouble switching from webapp to server for the primary routes, but trying again seems to have fixed it.) P.S. would be ideal to have a full GKE write-up in the docs since it's non-trivial to get it to play nicely as it stands today (at least when you're using private clusters and wanting to be able to leverage things like static reserved IP, Google-managed SSL cert, and IAP for auth using Google Accounts).

updated now and got rekt too haha I'm using the new [Gateway api](https://kubernetes.io/docs/concepts/services-networking/gateway/) instead of common Ingress though, so: 1. updated the HTTPRoute object - basically the Ingress instructions from [here](https://docs.airbyte.com/platform/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm) 2. dont forget to create the GKE "HealthCheckPolicy" so that the LB considers the new service as healthy (prevents the `no health upstream`message 3. if it's behind IAP (my case), dont forget to create the BackendPolicy for the connector builder + change the airbyte-webapp one to the server All done Gotchas this time: • builder broke, fixed as above • somehow the builder service turned into a `NodePort`service instead of

ClusterIP

- changed it back • this time around only the `airbyte-workload-api-server`didnt get its image tag updated and stayed on 1.6.0 instead of 1.7.2. sneaky sneaky