Happy Friday Airbyters! We're currently facing an issue deploying the Airbyte via helm chart within our internal AKS cluster. Our infrastructure team blocks us from pulling any image references which do not have the explicit registry prefix. (Basically, we need to prepend all of our image references with docker.io/ - for example we would need to reference docker.io/busybox:latest to pull the latest busybox image from within our K8s infrastructure due to a security policy which we cannot avoid). As a result of this policy, we are unable to proceed with our Airbyte deployment 😞 I've opened an issue here: https://github.com/airbytehq/airbyte/issues/21123 I'm willing to help out on this in any way I can as I would love to get Airbyte deployed on our k8s infrastructure asap. Any help is greatly appreciated thanku CC: @Tim Frazer

Hello Sean Glynn, it's been a while without an update from us. Are you still having problems or did you find a solution?

Hey Sajarin we managed to re-format the k8s policy which gave us a workaround