generate bundle: Option to use skopeo for resolving image digests
#6868
Comments
adambkaplan
changed the title
generate bundle: Option to use skopeo for pulling imagesgenerate bundle: Option to use skopeo for resolving image digests
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]>
2 tasks
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 bundlecommand hard-codescraneas 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
skopeoas 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.The text was updated successfully, but these errors were encountered: