Closed Mik4sa closed 1 year ago
- Which would be the right repo/image for windows?
registry.k8s.io/pause
ormcr.microsoft.com/oss/kubernetes/pause
they are both built from the same source. The difference is that the mcr.microsoft.com version has binaries signed by Microsoft. We typically reference the registry.k8s.io registries in the kuberentes repos.
I am not certian but I don't think '--pod-infra-container-image=mcr.microsoft.com/oss/kubernetes/pause:3.6
is used any more, the containerd configuration is what is used when deployed with containerd
I don't think it needs to be configured (custom containerd configurations are out of scope IMO) and should be the default that containerd version ships with.
I am not certian but I don't think
'--pod-infra-container-image=mcr.microsoft.com/oss/kubernetes/pause:3.6
is used any more, the containerd configuration is what is used when deployed with containerd
Looks like it's still in use See here: https://github.com/kubernetes/kubernetes/blob/7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647/pkg/kubelet/config/flags.go#L53-L54 and here: https://github.com/kubernetes/kubernetes/blob/7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647/cmd/kubelet/app/options/container_runtime.go#L25-L26
I don't think it needs to be configured (custom containerd configurations are out of scope IMO) and should be the default that containerd version ships with.
Ok, I'm fine with it. I'll then just change it manually for my clusters.
will be removed in a future release. Image garbage collector will get sandbox image information from CRI.
We should probably remove it since it is depreciated. That way we are proactive on it.
I'm unsure, but I think we can't remove it right now: https://github.com/kubernetes/kubernetes/pull/118544
In this kubernetes guide to configure
containerd
as the CRI runtime there is the following section:Currently our guide has no such section to inform about this. As far as I could see by just following the guide (as I did) we end with two different configured images. For containerD 1.7.1 the default configuration uses
registry.k8s.io/pause:3.8
In ourPrepareNode.ps1
script we usemcr.microsoft.com/oss/kubernetes/pause:3.6
: https://github.com/kubernetes-sigs/sig-windows-tools/blob/d744f5488dd350fa967b3920d698b268e214e14d/hostprocess/PrepareNode.ps1#L66This raises several questions:
registry.k8s.io/pause
ormcr.microsoft.com/oss/kubernetes/pause
registry.k8s.io/pause:3.9