You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 ^
What would you like to be added
Docker's standard naming convention for images is:
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.
The text was updated successfully, but these errors were encountered: