Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE Ability to alter the path of the oc-mirror stateful image on push #563

Closed
ianwatsonrh opened this issue Feb 14, 2023 · 4 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@ianwatsonrh
Copy link
Contributor

Version

Latest

What happened?

I'm mirroring the content into Quay. I'd like a exact match on the namespace/image combination for example if I'm mirroring registry.redhat.io/openshift-gitops-1/argocd-rhel8 then I'd like the path on Quay to be quay.example.com/openshift-gitops-1/argocd-rhel8.

I would use something like oc-mirror --from=. quay.example.com to perform the mirror.

The issue arises when oc-mirror attempts to verify/find the oc-mirror state container. As this will put use the path quay.example.com/oc-mirror as the location which isn't allowed in Quay due to the lack of namespace.

So to get around this the mirror command must be something like

oc-mirror --from=. quay.example.com/mirror to perform the mirror. This would then put the path of the container to quay.example.com/mirror/openshift-gitops-1/argocd-rhel8.

This isn't ideal as we're going to have a second batch of oc-mirroring being executed by using this Quay registry as a mirror of registry.redhat.io (think disconnected within disconnected within disconnected) all using quay.example.com as a proxy to registry.redhat.io.

What did you expect to happen?

Ideally I'd be able to specify a exact path for where I'd like the oc-mirror stateful container to go such as

oc-mirror --from=. --stateful-location=mirror/oc-mirror quay.example.com quay.example.com.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2023
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 15, 2023
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this as completed Jul 16, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jul 16, 2023

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants