feat(dvcr): auto-cleanup for dvcr storage

[diafour]

Description

A combination of 3 parts:

1. feat(dvcr): add controller to cleanup registry on schedule

• Add dvcr-maintenance controller tht triggers on schedule and secret/dvcr-maintenance changes.
  • Sets Maintenance condition on deployment/dvcr with cleanup state.
  • Creates secret to start cleanup, deletes secret when cleanup is finished.
• Add hook to switch deployment/dvcr into maintenance mode.
• Add spec.dvcr.gc.schedule setting to specify schedule in the ModuleConfig.
• Cleanup is disabled by default, set schedule explicitly in spec.settings.dvcr.gc.schedule to run cleanup periodically.

2. feat(api): postpone image operations until dvcr maintenance finishes (feat(api): postpone image operations until dvcr maintenance finishes #1689)

• Add postpone handler that runs before all other handlers.
• VirtualDisk: postpone only disks with dataSource that requires import to dvcr first.
• Add ProvisioningPostponed reason for Ready condition for vi/cvi/vd resources.

3. feat(core): add auto-cleanup and check commands in dvcr-cleaner (feat(core): add auto-cleanup and check for dvcr-cleaner #1675)

Add new commands to support auto-cleanup:

• dvcr-cleaner gc auto-cleanup — compares images in registry and in cluster, removes manifests not found in cluster, runs garbage collect.
• dvcr-cleaner gc check — jst compares images in registry and in cluster and prints images eligible to cleanup.

Why do we need it, and what problem does it solve?

We need to periodically cleanup non-existent images in registry to free up storage space.

What is the expected result?

dvcr storage is cleaned up on schedule.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: module
type: feature
summary: |
  Added the ability to clean up DVCR from non-existent project and cluster images:
  - By default, this feature is disabled.
  - To enable cleanup, set a schedule in the module settings: `.spec.settings.dvcr.gc.schedule`.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

all done.