Skip to content

Image push does not honor --insecure-skip-tls-verify #3724

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.

Sign up for GitHub

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

Jump to bottom
Closed
brandtkeller opened this issue Apr 23, 2025 · 0 comments · Fixed by #3725
Closed

Image push does not honor --insecure-skip-tls-verify #3724

brandtkeller opened this issue Apr 23, 2025 · 0 comments · Fixed by #3725
Labels
possible-bug 🐛

Comments

@brandtkeller
Copy link
Member

Steps to reproduce

  1. Zarf init to an external registry with self-signed certificates which are not trusted using the root --insecure-skip-tls-verify flag.

Expected result

Images can push to the registry

Actual Result

Issues with certificate trust during image push

Visual Proof (screenshots, videos, text, etc)

2025-04-23 17:30:41 ERR unable to deploy component "zarf-agent": unable to push images to the registry: failed to push image ghcr.io/zarf-dev/zarf/agent:v0.52.1: Head "https://default-route-openshift-image-registry.apps-crc.testing/v2/zarf-dev/zarf/agent/manifests/sha256:52448482eb7ccc5c6fa64c5546c265a3914ee8a2997bafb8e0c8f9771e1fad77": tls: failed to verify certificate: x509: certificate signed by unknown authority

Severity/Priority

Additional Context

the images PushConfig does not support passing in the flag - this should be a primary entrypoint to supporting this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
possible-bug 🐛
Projects
Zarf
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(images): support for insecure skip tls verify on image push/pull zarf-dev/zarf
1 participant
@brandtkeller