Has any one faced an issue of not being able to setup source connector when migrating from 1.x.x version to 2.0.0.

Hi Piyush, could you let me know what issue you are facing? I can take a look

Right now if my airbyte v2 values.yaml has auth enabled it does not let me run connections. Or set up source connectors. The workload laucnher pod does not trigger the pods responsible for starting a sync or setting up the destination conenctor.

I was able to find a github issue showing a similar issue: The problem is that the

WORKLOAD_API_BEARER_TOKEN

and

WORKLOAD_API_AUTH_HEADER

environment variables are passed to the workload-launcher, but not propagated to the connector-sidecar containers that the launcher creates. So when the sidecar tries to write results back to the workload API server, it gets a 401 Unauthorized and the job hangs or times out. The open GitHub issue tracking this: https://github.com/airbytehq/airbyte/issues/70451 As a workaround for now, if you disable auth in your values.yaml, connections and source setups should work normally. I know that's not ideal, but the auth token propagation to sidecars is a regression that the team is aware of. If disabling auth isn't an option for your environment, keep an eye on that GitHub issue for updates on a fix.

thank you