Open liangyuanpeng opened 7 months ago
Hi @liangyuanpeng ,thanks for your contributions, could you share the usage scenario and why to do it?
Since the karmadactl init component is serial, I would like to first pull all required container images before deploying to speed up the init process.
$ kubeadm config images list
registry.k8s.io/kube-apiserver:v1.30.0
registry.k8s.io/kube-controller-manager:v1.30.0
registry.k8s.io/kube-scheduler:v1.30.0
registry.k8s.io/kube-proxy:v1.30.0
registry.k8s.io/coredns/coredns:v1.11.1
registry.k8s.io/pause:3.9
registry.k8s.io/etcd:3.5.12-0
$ kubeadm config images list --image-repository=registry.k8s.io2
registry.k8s.io2/kube-apiserver:v1.30.0
registry.k8s.io2/kube-controller-manager:v1.30.0
registry.k8s.io2/kube-scheduler:v1.30.0
registry.k8s.io2/kube-proxy:v1.30.0
registry.k8s.io2/coredns:v1.11.1
registry.k8s.io2/pause:3.9
registry.k8s.io2/etcd:3.5.12-0
What would you like to be added:
Support command of
karmadactl config images list
Why is this needed: