hey! the only major problem we see from the experi...
# replication-troubleshooting
l
hey! the only major problem we see from the experience with airbyte - is minio we’re running airbyte at scale and so we constantly reach minio max storage. our logs is configured to use S3 but Airbyte seem to be still using minio for something called “storage state”. how can we remove this coupling and use S3 only?
k8s deployment
n
Hey Lior! I don't believe this is possible at this point, but let me look into it. Are you using kustomize or helm?
l
kustomize
n
From everything I'm seeing you should leave
WORKER_STATE_STORAGE_TYPE=MINIO
unchanged, and officially setting that to S3 is not supported. https://discuss.airbyte.io/t/worker-process-of-airbyte-v0-40-9-fails-to-start-on-custom-s3-config/2849/12 I did find another user that's running into the same issue as you and this was the workaround for them: https://discuss.airbyte.io/t/how-to-clean-up-airbyte-minio-and-whats-stored-in-minio/3101/5?u=natalyjazzviolin
l
thanks!