Am Mittwoch, dem 03.03.2021 um 08:59 +0100 schrieb Robert Munteanu:

Hi,

After some trouble with one of my kubic clusters [1] I was told to ask here regarding the retention policy for registry.opensuse.org container images.

My cluster went down because I was still running an 'old' set of images, e.g. registry.opensuse.org/kubic/kube-proxy:v1.19.4 and, for some reason, the image was no longer available on the node after a restart. At the time of the discusison, v1.19.4 was gone and v1.19.7 was available on registry.o.o .

Can this retention policy be tweaked?

Short answer: No registry.opensuse.org is only a proxy for build.opensuse.org - If the package gets deleted from  https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed the built containers are no longer available on registry.opensuse.org. If packages are deleted or not is decision of the maintainers of the project and has nothing to do with registry.opensuse.org or build.opensuse.org.

I would imagine it would be beneficial for users of kubic to have the images available for a longer time. I don't dare say forever as I'm not aware of the impact that has, but it would definitely be the nicest.

For the record, these are the images that are stored on registry.o.o for my cluster:

$ kubectl get pod -A -o jsonpath='{range .items[*].spec.containers[*]} {.image}{"\n"} {end}' | grep registry.opensuse | sort -u   registry.opensuse.org/kubic/coredns:1.7.0   registry.opensuse.org/kubic/etcd:3.4.13-0   registry.opensuse.org/kubic/kube-apiserver:v1.20.2   registry.opensuse.org/kubic/kube-controller-manager:v1.20.2   registry.opensuse.org/kubic/kube-proxy:v1.20.2   registry.opensuse.org/kubic/kube-scheduler:v1.20.2   registry.opensuse.org/kubic/weave-kube:2.8.1   registry.opensuse.org/kubic/weave-npc:2.8.1

Thanks, Robert

[1]: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/RJT...