Hi guys! We have deployed airbyte in k8s. Our cluster policy is that we can't deploy pods that point to public images and also the pod should run as

non-root.

Have made the necessary changes to fulfill our cluster policy and all airbyte services have been successfully deployed and running. But now we have another blocker due to run as

non-root

policy. I'm adding a new connector from the UI (in order to point the image to our private registry) but the pod that gets deployed in order to add this new connector is failing to start due to

non-root

policy

Error: container has runAsNonRoot and image will run as root (pod: "source-mssql-spec-1dfbbc78-d22d-4cc6)

The image is trying to run as

root

The image is a copy of

airbyte/source-mssql:0.3.22

public image. Anyone has encounter this issue before and was able to resolve?

Hello Tomas, there is one issue open about the platform containers but none requesting for connectors. Not sure if it's possible to change user in connector container easily too.

Right. Ok thanks!