Skip to content

Conversation

@deepsm007
Copy link
Contributor

@deepsm007 deepsm007 commented Nov 18, 2025

Updates garbage collection for orphaned ReleasePayloads to use a coordinated deletion mechanism via remove__ prefixed tags, allowing the pruner to handle tag deletion. Update AlternateImageRepository example to reflect quay.io/openshift/ci as the default destination.

/cc @bradmwilliams

/hold

@openshift-ci openshift-ci bot requested a review from bradmwilliams November 18, 2025 21:38
@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 18, 2025
@deepsm007 deepsm007 force-pushed the DPTP-4340-promotion branch 3 times, most recently from 2f11fba to cada9b8 Compare November 18, 2025 22:39
// will mirror Accepted releases to.
// For example:
// "alternateImageRepository": "quay.io/openshift-release-dev/dev-release"
// "alternateImageRepository": "quay.io/openshift/ci"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is literally just a comment reference. If/when this goes live, you'll need to update all the respective references, like here: https://github.com/openshift/release/blob/6e2ede7d8f765e123cb1c0cfaf33f80a92a2b9e5/core-services/release-controller/_releases/release-ocp-4.21-ci.json#L10-L11

…nated deletion via remove__ prefixed tags in quay.io
@deepsm007 deepsm007 force-pushed the DPTP-4340-promotion branch from cada9b8 to f05cd7d Compare December 5, 2025 18:00
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: deepsm007
Once this PR has been reviewed and has the lgtm label, please ask for approval from bradmwilliams. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 5, 2025

@deepsm007: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/govulncheck f05cd7d link false /test govulncheck
ci/prow/security f05cd7d link false /test security

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

jobName := fmt.Sprintf("%s-remove-tag", payload.Name)
return c.ensureJob(jobName, nil, func() (*batchv1.Job, error) {
// Get cli image from mirror or config
cliImage := "registry.ci.openshift.org/ocp/4.16:cli"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Don't like this being hard-coded
  2. If it must be hard-coded, then it should, at least, point to a more modern version (like: 4.21)


job, prefix := newReleaseJobBase(jobName, cliImage, release.Config.AlternateImageRepositorySecretName)

rcPayloadTag := fmt.Sprintf("rc_payload__%s", payload.Name)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We currently do not create release tags named anything like: rc_payload__{version}, so this logic does not make any sense to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will be using similar here

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused...
Based on this logic, the calculated "fromImage" will be something of the form: rc_payload__4.22.0-0.nightly-2025-12-17-101159
Which will be passed into oc mirror <FROM> <TO>, correct?
What I'm questioning is why you think the "FROM" image even exists with that naming convention?
AFAIK, the release-controller doesn't have any logic to create such a named release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants