Skip to content

generate bundle: Option to use skopeo for resolving image digests #6868

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

Closed
adambkaplan opened this issue Nov 19, 2024 · 4 comments
Closed

generate bundle: Option to use skopeo for resolving image digests #6868

adambkaplan opened this issue Nov 19, 2024 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@adambkaplan
Copy link

Feature Request

Describe the problem you need a feature to resolve.

I have an issue digest-pinning my operator CSV images when using a mirror or leveraging Podman's image registry re-mapping feature (Red Hat blog explaining the feature). This is useful when my images are being pushed to a dev or staging registry, and the production release process is a simple matter of mirroring release candidate images.

The current generate bundle command hard-codes crane as the tool to resolve container image digests, and operator-sdk has no ability to configure image registry mirrors.

Describe the solution you'd like.

Provide an option to use skopeo as the tool for resolving image digests. This would allow me to take advantage of Podman's existing configuration for registry mirrors and registry re-mapping.

@adambkaplan adambkaplan changed the title generate bundle: Option to use skopeo for pulling images generate bundle: Option to use skopeo for resolving image digests Nov 19, 2024
adambkaplan added a commit to adambkaplan/operator-sdk that referenced this issue Nov 19, 2024
Add option to select the image digest resolver when rendering bundles with
image digests pinned. The set of supported tools is defined in the
`operator-manifest-tools` library (curretnly `crane`, `skopeo`, and `script`).

Fixes operator-framework#6868

Signed-off-by: Adam Kaplan <[email protected]>
adambkaplan added a commit to adambkaplan/operator-sdk that referenced this issue Nov 19, 2024
Add option to select the image digest resolver when rendering bundles with
image digests pinned. The set of supported tools is defined in the
`operator-manifest-tools` library (currently `crane`, `skopeo`, and `script`).

Fixes operator-framework#6868

Signed-off-by: Adam Kaplan <[email protected]>
@openshift-bot
Copy link

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 Feb 18, 2025
@openshift-bot
Copy link

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 Mar 20, 2025
@openshift-bot
Copy link

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 Apr 20, 2025
Copy link

openshift-ci bot commented Apr 20, 2025

@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-sigs/prow 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

Successfully merging a pull request may close this issue.

2 participants