Improve UX to inform users that container registry cleanup policies are automatically disabled on GitLab.com

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Context

From slack(internal)

we are noticing that some projects are regularly disabling their container cleanup policy. For example, the cleanup policies got enabled (again) about an hour ago on these projects by our terraform pipeline. I also checked that the cleanup policy was in fact enabled and now they got disabled again and got re-enabled when I ran the terraform pipeline again. Is there anything known that automatically disables container cleanup policies in projects?

https://docs.gitlab.com/ee/user/packages/container_registry/reduce_container_registry_storage.html#enable-the-cleanup-policy:

For performance reasons, enabled cleanup policies are automatically disabled for projects on GitLab.com that don’t have a container image.

Proposal

We need to improve UX to inform users that container registry cleanup policies are automatically disabled on GitLab.com

Based on suggestion, it'll be good to explore how to surface this on the UI on the cleanup settings page & not only the docs.