why kubernetes images url format is `<registry_url>/<image_name>:<image_tag>` about registry.k8s.io HOT 4 CLOSED

and final it cause me must use docker registry (registry:2), because harbor only support format2.

that sounds like a missing flexibility in harbor.

suggest

it does make sense to have the subpath consistency, but we cannot just move the images to the new location.
they likely have to be mirrored first, and if we decide to migrate users to the new location it will be a long process.

kubespray offline design

kubespray uses kubeadm and kubeadm's imageRepositry API field can technically accept a "repo/path" format and not only "repo". the problem will be with coredns images that will become "repo/path/coredns" which will not be valid unless you pushed coredns to that path instead of "repo/coredns". the kubeadm API has individual field for DNS that can be used to override the coredns image path, though.

from registry.k8s.io.

• that sounds like a missing flexibility in harbor.
  yes ,but i think harbor will not support push image without project name, it have a web ui to list and manage all projects, no project name will cause the ui list to become confused.

• it does make sense to have the subpath consistency

there just have 6 images use short format(Except coredns), and only k8s have this short format ,hope have a change in furture

root@node51:~# kubeadm config images list
I0117 09:21:50.999039 1387839 version.go:256] remote version is much newer: v1.26.0; falling back to: stable-1.25
registry.k8s.io/kube-apiserver:v1.25.5
registry.k8s.io/kube-controller-manager:v1.25.5
registry.k8s.io/kube-scheduler:v1.25.5
registry.k8s.io/kube-proxy:v1.25.5
registry.k8s.io/pause:3.8
registry.k8s.io/etcd:3.5.6-0
registry.k8s.io/coredns/coredns:v1.9.3

• kubespray uses kubeadm and kubeadm's imageRepositry

yes ,So this is the problem caused by inconsistency

from registry.k8s.io.

Those 6 images are available in two formats, however this is not up to registry.k8s.io, it's up to SIG release publishing them in the backing store.

Harbor should fix this, because it's fully in compliance with OCI distribution to just have host/image:tag AFAIK, and Kubernetes has been doing this a long time. registry.k8s.io has the exact same image names as k8s.gcr.io, by design.

from registry.k8s.io.

FYI @kubernetes/sig-release @kubernetes/release-engineering

Kubernetes does not currently plan to remove the short format for consistency reasons, it has been around a long time.

You could file a bug with kubernetes/release and kubernetes/kubeadm to ask the respective projects to switch to only the nested format, but it will remain for all existing Kubernetes minor versions, and registry.k8s.io infrastructure will remain unchanged.

from registry.k8s.io.