Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed
--insecureflag for mirror pushUpdated the
github.com/deckhouse/deckhouse/pkg/registrydependency to the fixed version that properly handles the--insecureflag.Problem
The
--insecureflag was being ignored when pushing to HTTP registries, causing TLS errors even when users explicitly requested insecure connections.Root Cause
The registry client dependency had a bug that unconditionally reset
opts.Insecure = false, preventing HTTP connections to insecure registries.Solution
Updated the dependency to include the fix from deckhouse/deckhouse#17554
Testing
The bug only affects real hostnames and public IPs. It doesn't affect
localhost,127.0.0.1, or private IPs because go-containerregistry automatically uses HTTP for these addresses.To test with localhost, add a custom hostname to
/etc/hosts: