@kapa.ai is it safe to clear logs stored in

/storage/airbyte-bucket/job-logging/

? running airbyte 2 on k8s

Yes, it is generally safe to clear the logs under that path, with a couple of caveats. From similar Kubernetes setups using MinIO/S3-compatible storage, users have resolved “storage full” and hanging sync issues by deleting job logs under the MinIO bucket paths such as: -

/storage/airbyte-storage/job-logging/workspace

-

/storage/airbyte-dev-logs/job-logging/workspace/

[[Minio storage full](https://discuss.airbyte.io/t/1857); [Clean up airbyte-minio](https://discuss.airbyte.io/t/3101)] These locations store sync/job logs and related workspace output, not your connector configurations or actual replicated data. Deleting them frees space but only removes historical logs; it does not delete sources, destinations, connections, or data in your destination warehouse/lake. [[Minio storage full](https://discuss.airbyte.io/t/1857); [All sync jobs hanging](https://github.com/airbytehq/airbyte/issues/55812)] So for Airbyte 2 on Kubernetes, you can: - Safely delete objects under your

job-logging

prefix (e.g.

/storage/airbyte-bucket/job-logging/…

) to reclaim space, understanding you’ll lose those past logs. - Optionally tune retention to avoid this in the future (e.g.

TEMPORAL_HISTORY_RETENTION_IN_DAYS

) as shown in similar setups. [[Airbyte log sweeping](https://discuss.airbyte.io/t/2714); [All sync jobs hanging](https://github.com/airbytehq/airbyte/issues/55812)] If you rely on old logs for auditing or debugging, consider copying them elsewhere before deletion.