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

Support for Non-Standard Repository Names in Image Pull #11869

Open
VrindaMarwah opened this issue Jan 8, 2025 · 1 comment
Open

Support for Non-Standard Repository Names in Image Pull #11869

VrindaMarwah opened this issue Jan 8, 2025 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@VrindaMarwah
Copy link

VrindaMarwah commented Jan 8, 2025

What would you like to be added

Docker's standard naming convention for images is:

<registry>/<namespace>/<repository>:<tag>

For e.g docker.io/kubernetesui/dashboard:v2.7.0

However, some container registries (e.g., Pulp) might store images in a non-standard naming convention, such as referencing only the tag (v2.7.0) without including the full / hierarchy.

Does Kubespray support pulling images from such registries where the repository names differ from the standard Docker naming convention? If not, are there any workarounds or recommendations for using Kubespray with such repositories?

Why is this needed

Some container registries (e.g., Pulp) might store images in a non-standard naming convention, such as referencing only the tag (v2.7.0) without including the full / hierarchy.

@VrindaMarwah VrindaMarwah added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 8, 2025
@VannTen
Copy link
Contributor

VannTen commented Jan 9, 2025

Does Kubespray support pulling images from such registries where the repository names differ from the standard Docker naming convention? If not, are there any workarounds or recommendations for using Kubespray with such repositories?

Hum, did you try it ? We mostly pass the image ref to the underlying tool, so there is a good change it just works.
Not sure if we do some manipulation which assume a particular format in download role somewhere, best to try ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants