Skip to content

Remove the container_registry_expiration_policies_caching feature flag

David Fernandez requested to merge 340606-feature-flag-cleanup into master

🍍 Context

In !69459 (merged), we added a caching feature to cleanup policies for container images to speed up their executions.

That change was quite a deep one and so, we deployed it behind a feature flag: container_registry_expiration_policies_caching.

The rollout went well and has been enabled for a full milestone on gitlab.com.

It is now time to remove it from the codebase.

⚠ Please note that this feature flag is nested in another one that is more general (it gates all the work around conserving resources when executing cleanup policies. Read more about it here).

Being a "nested" feature flag, I don't think we need a changelog here.

Related rollout issue: https://gitlab.com/gitlab-org/gitlab/-/issues/340606.

🔬 What does this MR do and why?

  • Remove the container_registry_expiration_policies_caching feature flag
  • Update the related specs

🖼 Screenshots or screen recordings

n / a

⛓ How to set up and validate locally

See !69459 (diffs)

✅ MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports