Thanks for your feedback. I’d suggest starting the analysis to identify the type of most storage being consumed. Maybe CI/CD job artifacts are kept forever and

Thanks for your feedback. I’d suggest starting the analysis to identify the type of most storage being consumed. Maybe CI/CD job artifacts are kept forever and need an expiration configuration [0], or container images in the registry would need cleanup policies [1]. The documentation linked in the FAQ provides more analysis and guides to help. [2] If you need additional help with analyzing the storage usage, please contact the GitLab support team. You can also post cleanup questions on our community forum. [3] [0] https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#when-job-artifacts-are-deleted https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#w... [1] https://docs.gitlab.com/ee/user/packages/container_registry/reduce_container_registry_storage.html https://docs.gitlab.com/ee/user/packages/container_registry/... [2] https://about.gitlab.com/pricing/faq-paid-storage-transfer/#managing-your-storage-usage https://about.gitlab.com/pricing/faq-paid-storage-transfer/#... [3] https://forum.gitlab.com/c/gitlab-ci-cd/23 https://forum.gitlab.com/c/gitlab-ci-cd/23