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

Avoid registry fallback #2445

Closed
fgiannetti opened this issue Mar 24, 2023 · 0 comments · Fixed by #2637
Closed

Avoid registry fallback #2445

fgiannetti opened this issue Mar 24, 2023 · 0 comments · Fixed by #2637
Labels
kind/feature-request kind/question Further information is requested needs-discussion Items which need more discussion before commitment priority/p2 High impact feature/bug. Will get a lot of users happy
Milestone

Comments

@fgiannetti
Copy link
Contributor

Hi all!
I want to use a private registry in Kaniko, but only that registry.

I am implementing an image whitelist in the private registry, but when i return a 403 for a non whitelisted image, Kaniko fallback to dockerhub and the image is pulled from there anyway.
Is there a way to prevent this behavior?

Im using the --registry-mirror argument with the private registry address

Thanks very much in advance!

@fgiannetti fgiannetti changed the title Avoid regostry fallback Avoid registry fallback Mar 24, 2023
@aaron-prindle aaron-prindle added kind/question Further information is requested kind/feature-request needs-discussion Items which need more discussion before commitment priority/p2 High impact feature/bug. Will get a lot of users happy labels Jun 21, 2023
@aaron-prindle aaron-prindle added this to the v1.13.0 milestone Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request kind/question Further information is requested needs-discussion Items which need more discussion before commitment priority/p2 High impact feature/bug. Will get a lot of users happy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants