Skip to content

Conversation

@tchap
Copy link
Contributor

@tchap tchap commented Jul 9, 2025

Move to use upstream distribution/v3 instead of our private fork.

This is blocked by openshift/library-go#1972

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 9, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 9, 2025

@tchap: This pull request references WRKLDS-1599 which is a valid jira issue.

In response to this:

Move to use upstream distribution/v3 instead of our private fork.

This is blocked by openshift/library-go#1972

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from bparees and deads2k July 9, 2025 12:41
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 9, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@tchap tchap force-pushed the distribution-v3 branch from 97e311b to e017e58 Compare July 10, 2025 08:20
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2025

@tchap: 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/e2e-aws-ovn-serial e017e58 link true /test e2e-aws-ovn-serial
ci/prow/okd-scos-e2e-aws-ovn e017e58 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-cmd e017e58 link false /test e2e-aws-ovn-cmd
ci/prow/e2e-aws-ovn-serial-1of2 e017e58 link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-tests-extension e017e58 link true /test e2e-tests-extension

Full PR test history. Your PR dashboard.

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.


"github.com/openshift/library-go/pkg/image/reference"
"github.com/openshift/library-go/pkg/image/registryclient"
registryclient "github.com/openshift/library-go/pkg/image/registryclient/v2"
Copy link
Member

Choose a reason for hiding this comment

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

isn't this package already called registryclient?

// imageIndexJSON actually contains the same manifests as manifestListJSON,
// so the same manifests can be used during testing.
//
//go:embed testdata/image-index.json
Copy link
Member

Choose a reason for hiding this comment

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

why did we need to create a copy of manifestListJSON ? 🤔

_, isIndex := manifest.(*ocischema.DeserializedImageIndex)
_, isList := manifest.(*manifestlist.DeserializedManifestList)
if isIndex || isList {
if importMode != "" && importMode != imageapi.ImportModeLegacy {
Copy link
Member

Choose a reason for hiding this comment

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

I think placing the these checks into a variable makes the condition considerably easier to read.
i.e.:

legacyManifestListImport := importMode == "" || importMode == imageapi.ImportModeLegacy
// ...
    if !legacyManifestListImport {
        // ...
    } 

What do you think?

return manifestToImage(manifest, d)
}

manifest, d, err = selectManifestForPlatform(ctx, manifest, ref, s, preferArch, preferOS)
Copy link
Member

Choose a reason for hiding this comment

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

This is a much better name for manifestFromManifestList, thanks!

@flavianmissi
Copy link
Member

I really like the refactorings you made here @tchap.
Unfortunately, the greater the refactor the greater the risk. This means we need to help QE decide what exactly they need to test.
Could you enumerate the user impact of the changes in this PR? I can definitely help if needed, but it would be nice if you could get something going.
Thanks again for taking care of this!

@tchap
Copy link
Contributor Author

tchap commented Oct 27, 2025

@flavianmissi I see you woke up after some time 🙂

I think that I put this to rest for now because I was blocked on rebase for apiserver-library-go or something. This change is rather complex across multiple repositories. But I can try to check the status this week or potentially the next, I am working on some Kubernetes stuff right now.

@flavianmissi
Copy link
Member

no rush, I'll be off most of november so won't be able to review anything more anyway. let's catch up later.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants