1. Proposed title of this feature request
Mirror Platform-Specific Images Only; Remove Irrelevant Images from Private Registry

2. What is the nature and description of the request?
The whole requirement and expectation from Customer is ,why should we download and host the unused images in our env and track the CVE associated with those unused images in our books.

This feature request is to enhance the mirroring process by allowing filtering and retention of only platform-specific images in a private mirror registry. Currently, the mirroring process pulls images for multiple platforms (e.g., AWS, GCP, Bare Metal), regardless of the target deployment platform, leading to unnecessary image bloat in the registry.

The goal is to either:

• Mirror only the images specific to the selected platform (e.g., only AWS-related images for an AWS deployment),
  OR

• Remove unrelated or unused images from the private mirror registry after mirroring, ensuring that only platform-specific images are retained.

For example, in an AWS environment, images meant for GCP, VMware, or Bare Metal should not be mirrored or should be removed if not applicable.

This will help optimize storage usage, reduce mirror size, and simplify registry maintenance.

3. Why does the customer need this? (List the business requirements here)
Audit requirement to have Zero CVE critical systems, however the most of the CVE's are reporting from the unused images , so requirement to filter the unused images and produce the CVE reports with audit teams with correct information of the system.

4. List any affected packages or components.
-