You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Summary
This pull request introduces a new script and corresponding Evergreen
tasks to backup digest-pinned images from a ClusterServiceVersion (CSV)
YAML file to Quay.io. The changes include adding a Python script to
perform the backup process, new Evergreen tasks to execute the script,
and a new build variant for these tasks.
### New Evergreen tasks and build variant:
*
[`.evergreen.yml`](diffhunk://#diff-9a7744843f307953832ec106e8d49be546037475db24ec6873e5fec6249c236dR608-R647):
Added three new tasks (`backup_csv_images_dry_run`,
`backup_csv_images_limit_3`, and `backup_csv_images_all`) to run the
backup script with different options, and created a new build variant
(`backup_csv_images`) to group these tasks under the "Backup CSV Images"
workflow.
[[1]](diffhunk://#diff-9a7744843f307953832ec106e8d49be546037475db24ec6873e5fec6249c236dR608-R647)
[[2]](diffhunk://#diff-9a7744843f307953832ec106e8d49be546037475db24ec6873e5fec6249c236dR1245-R1255)
### New Python script for image backup:
*
[`scripts/dev/release/backup_csv_images.py`](diffhunk://#diff-cd0fc9d64b8e8c03c901ad1ebcba9734985ab170613937b2b0e7dcb91b94037cR1-R370):
Added a comprehensive Python script to parse a CSV file, extract
digest-pinned images, and back them up to Quay.io using a new tag format
(`_openshift_<mck_version>`). The script supports dry-run mode, logging,
and limiting the number of images to back up.
## Proof of Work
https://parsley.mongodb.com/evergreen/mongodb_kubernetes_backup_csv_images_backup_csv_images_all_patch_5710105f0347aed651ce63e6b37f06051caa634a_686e4ee749d2610007d96aaa_25_07_09_11_13_48/0/task?bookmarks=0,11182&shareLine=3143


## Checklist
- [x] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you checked for release_note changes?
## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
* **blocking**: Must be addressed before approval.
* **follow-up**: Can be addressed in a later PR or ticket.
* **q**: Clarifying question.
* **nit**: Non-blocking suggestions.
* **note**: Side-note, non-actionable. Example: Praise
* --> no prefix is considered a question
0 commit comments