March 2021 - openSUSE Build Service - openSUSE Mailing Lists

Create a SR to add a linked package to a project?
by Johannes Kastl 05 Mar '21

05 Mar '21

Hi all, sorry if this is an old hat, but my google-foo left me: Can I create a SR to add a linkpac'ed package to a project? The end result (after someone accepts the SR) should be that the package in the project should be a link to some other package. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

1 0

Re: Retention policy of container images from registry.opensuse.org
by Frank Schreiner 03 Mar '21

03 Mar '21

Am Mittwoch, dem 03.03.2021 um 09:48 +0100 schrieb Richard Brown: > > > Hi Frank, > > Robert isn't asking for the retention of containers when they are > removed from > https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed > > Robert is asking for a longer retention of containers with old tags > from > https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed > when they are superseded with new containers with new tags > > Currently registry.opensuse.org has a period where both 'old tag' > containers and 'current tag' containers coexist. As I already tried to point out - there is no such period. If you delete e.g. the "package" kubic-kube-proxy-minus1-image.20210114151709 at least tag kubic/kube-proxy:v1.19.6-2.1000 will be gone. If you delete kubic-kube-proxy-minus1-image.20210108134717 kubic-kube-proxy-minus1-image.20210114151709 kubic-kube-proxy-minus1-image.20210126101702 the tag kubic/kube-proxy:v1.19.6 will be gone - because it occurs in all this packages.

1 0

Retention policy of container images from registry.opensuse.org
by Robert Munteanu 03 Mar '21

03 Mar '21

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? 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/RJ…

2 1