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

Bug: Proxy with private repository #1622

Closed
Despire opened this issue Dec 26, 2024 · 1 comment
Closed

Bug: Proxy with private repository #1622

Despire opened this issue Dec 26, 2024 · 1 comment
Labels
bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper

Comments

@Despire
Copy link
Contributor

Despire commented Dec 26, 2024

Current Behaviour

It seems that the proxy settings does not seem to work well when downloading images from private repositories.

Expected Behaviour

Downloading images from both public and private repositories should work.

@Despire Despire added the bug Something isn't working label Dec 26, 2024
@bernardhalas bernardhalas added the groomed Task that everybody agrees to pass the gatekeeper label Jan 10, 2025
@bernardhalas
Copy link
Member

By its own very nature, the installation proxy service has a whitelist of domains that it's allowed to open outgoing connections to. In this whitelist we currently maintain the necessary upstream artifactories, registries and repositories that are necessary for spawning a Kubernetes cluster successfully.

Of course, if one wishes to use private image registry, the expectation is that it's not whitelisted by default (as it can be hosted on any arbitrary hostname). Therefore, private registry URLs need to be added to proxy whitelist on request by Berops engineering team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working groomed Task that everybody agrees to pass the gatekeeper
Projects
None yet
Development

No branches or pull requests

2 participants