Proposal for ch-k8s-lbaas clean up
Hi everyone, the Tarook team has decided to take over maintenance of its LBaaS component, ch-k8s-lbaas[0]. It has been forked into the Tarook namespace[1] and will continue[2] under the name "tarook-lb". For various historic reasons, there are two diverged forks of it in the Yaook group (yaook/ch-k8s-lbaas and yaook/images/ch-k8s-lbaas). yaook/ch-k8s-lbaas is de facto used as an alternative container registry, with copies of the upstream images being hosted (but not build) there. yaook/images/ch-k8s-lbaas was never used for anything, AFAIK. To avoid confusion and safe precious maintainer time & resources, I propose to replace the yaook/ch-k8s-lbaas repo content with a discontinuation notice, and archive the project. That will preserve the container registry, so Tarook can still pull the images from there: https://gitlab.com/yaook/ch-k8s-lbaas/-/merge_requests/36 yaook/images/ch-k8s-lbaas should IMHO get deleted, but we may rather archive it to play it safe. To make sure I didn't miss anything, I think it would be good if project representatives of both Yaook and Tarook sign off on this plan, before someone with the necessary permissions (not me^^) goes ahead with it. Best regards Friedrich [0]: https://github.com/cloudandheat/ch-k8s-lbaas [1]: https://gitlab.com/alasca.cloud/tarook/tarook-lb [2]: https://gitlab.com/alasca.cloud/tarook/meta/-/work_items/8
Hi lists, On Dienstag, 10. November 2026 14:50:38 Mitteleuropäische Normalzeit Friedrich Zahn via Tarook wrote:
the Tarook team has decided to take over maintenance of its LBaaS component, ch-k8s-lbaas[0]. It has been forked into the Tarook namespace[1] and will continue[2] under the name "tarook-lb".
For various historic reasons, there are two diverged forks of it in the Yaook group (yaook/ch-k8s-lbaas and yaook/images/ch-k8s-lbaas).
yaook/ch-k8s-lbaas is de facto used as an alternative container registry, with copies of the upstream images being hosted (but not build) there. yaook/images/ch-k8s-lbaas was never used for anything, AFAIK.
To avoid confusion and safe precious maintainer time & resources, I propose to replace the yaook/ch-k8s-lbaas repo content with a discontinuation notice, and archive the project. That will preserve the container registry, so Tarook can still pull the images from there: https://gitlab.com/yaook/ch-k8s-lbaas/-/merge_requests/36
yaook/images/ch-k8s-lbaas should IMHO get deleted, but we may rather archive it to play it safe.
To make sure I didn't miss anything, I think it would be good if project representatives of both Yaook and Tarook sign off on this plan, before someone with the necessary permissions (not me^^) goes ahead with it.
With the little authority I have, I say that YAOOK has no stakes in ch- k8s-lbaas, so I approve of this plan (and I'd even say to delete the images/ch-k8s-lbaas repository, if it contains no images). I have the necessary privileges to execute this plan and can do so once TAROOK green-lights it. kind regards, -- Jonas Schäfer CTO Business Unit Cloud Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schaefer@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann
Hi Yaook and Tarook list, the proposed plan is also fine for me, I would be also fine with deleting both repositories, but seems like that yaook/ch-k8s-lbaas is still somehow used, if I got your message correctly (I didn'g checked myself.) Regards Stefan On 11/10/26 17:32, Jonas Schäfer via Yaook wrote:
Hi lists,
On Dienstag, 10. November 2026 14:50:38 Mitteleuropäische Normalzeit Friedrich Zahn via Tarook wrote:
the Tarook team has decided to take over maintenance of its LBaaS component, ch-k8s-lbaas[0]. It has been forked into the Tarook namespace[1] and will continue[2] under the name "tarook-lb".
For various historic reasons, there are two diverged forks of it in the Yaook group (yaook/ch-k8s-lbaas and yaook/images/ch-k8s-lbaas).
yaook/ch-k8s-lbaas is de facto used as an alternative container registry, with copies of the upstream images being hosted (but not build) there. yaook/images/ch-k8s-lbaas was never used for anything, AFAIK.
To avoid confusion and safe precious maintainer time & resources, I propose to replace the yaook/ch-k8s-lbaas repo content with a discontinuation notice, and archive the project. That will preserve the container registry, so Tarook can still pull the images from there: https://gitlab.com/yaook/ch-k8s-lbaas/-/merge_requests/36
yaook/images/ch-k8s-lbaas should IMHO get deleted, but we may rather archive it to play it safe.
To make sure I didn't miss anything, I think it would be good if project representatives of both Yaook and Tarook sign off on this plan, before someone with the necessary permissions (not me^^) goes ahead with it. With the little authority I have, I say that YAOOK has no stakes in ch- k8s-lbaas, so I approve of this plan (and I'd even say to delete the images/ch-k8s-lbaas repository, if it contains no images).
I have the necessary privileges to execute this plan and can do so once TAROOK green-lights it.
kind regards,
_______________________________________________ Yaook mailing list -- yaook@lists.alasca.cloud To unsubscribe send an email to yaook-leave@lists.alasca.cloud
-- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann
Hi, On 11/11/26 14:16, Stefan Hoffmann via Tarook wrote:
the proposed plan is also fine for me, I would be also fine with deleting both repositories, but seems like that yaook/ch-k8s-lbaas is still somehow used, if I got your message correctly (I didn'g checked myself.) I probably should have made that more clear, the yaook/ch-k8s-lbaas has to be preserved and can't be deleted. Its container registry is currently the default image source for the Tarook LBaaS service layer, so its critical for all Tarook clusters with that enabled.
Best regards Friedrich
Does it still work, if we set the repository to archived? On 11.11.26 14:37, Friedrich Zahn via Yaook wrote:
Hi,
On 11/11/26 14:16, Stefan Hoffmann via Tarook wrote:
the proposed plan is also fine for me, I would be also fine with deleting both repositories, but seems like that yaook/ch-k8s-lbaas is still somehow used, if I got your message correctly (I didn'g checked myself.) I probably should have made that more clear, the yaook/ch-k8s-lbaas has to be preserved and can't be deleted. Its container registry is currently the default image source for the Tarook LBaaS service layer, so its critical for all Tarook clusters with that enabled.
Best regards Friedrich _______________________________________________ Yaook mailing list -- yaook@lists.alasca.cloud To unsubscribe send an email to yaook-leave@lists.alasca.cloud
-- Stefan Hoffmann DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 36 stefan.hoffmann@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann
Hi, On 11/12/26 10:48, Stefan Hoffmann wrote:
Does it still work, if we set the repository to archived? Yes, both according to the docs[0], and also looking at other archived projects, e.g.: https://gitlab.com/yaook/images/neutron-ovn-agent/container_registry/3893409 I am still able to pull an image from there.
Archiving is also very easy to reverse, if any problems should surface. Deleting is also reversible on GitLab.com btw, by default it does an immediate soft-delete and then hard-deletes the project after 30 days. Best regards Friedrich [0]: https://docs.gitlab.com/user/project/working_with_projects/#archive-a-projec...
Hi, please defer from deleting (or archiving) any repositories for now. We're currently lacking resources to lock into that in detail. Best regards Steve On 10.11.26 17:32, Jonas Schäfer via Tarook wrote:
Hi lists,
On Dienstag, 10. November 2026 14:50:38 Mitteleuropäische Normalzeit Friedrich Zahn via Tarook wrote:
the Tarook team has decided to take over maintenance of its LBaaS component, ch-k8s-lbaas[0]. It has been forked into the Tarook namespace[1] and will continue[2] under the name "tarook-lb".
For various historic reasons, there are two diverged forks of it in the Yaook group (yaook/ch-k8s-lbaas and yaook/images/ch-k8s-lbaas).
yaook/ch-k8s-lbaas is de facto used as an alternative container registry, with copies of the upstream images being hosted (but not build) there. yaook/images/ch-k8s-lbaas was never used for anything, AFAIK.
To avoid confusion and safe precious maintainer time & resources, I propose to replace the yaook/ch-k8s-lbaas repo content with a discontinuation notice, and archive the project. That will preserve the container registry, so Tarook can still pull the images from there: https://gitlab.com/yaook/ch-k8s-lbaas/-/merge_requests/36
yaook/images/ch-k8s-lbaas should IMHO get deleted, but we may rather archive it to play it safe.
To make sure I didn't miss anything, I think it would be good if project representatives of both Yaook and Tarook sign off on this plan, before someone with the necessary permissions (not me^^) goes ahead with it. With the little authority I have, I say that YAOOK has no stakes in ch- k8s-lbaas, so I approve of this plan (and I'd even say to delete the images/ch-k8s-lbaas repository, if it contains no images).
I have the necessary privileges to execute this plan and can do so once TAROOK green-lights it.
kind regards,
_______________________________________________ Tarook mailing list -- tarook@lists.alasca.cloud To unsubscribe send an email to tarook-leave@lists.alasca.cloud
-- Steve Starke Team Lead Kubernetes Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 00 steve.starke@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann
participants (4)
-
Friedrich Zahn -
Jonas Schäfer -
Stefan Hoffmann -
Steve Starke