September 2026 - Tarook - lists.alasca.cloud

Re: Topic for shore leave - future of ch-k8s-lbaas

by Friedrich Zahn

Hi everyone, On 9/11/26 10:16, Friedrich Zahn via Tarook wrote: > I would like to give you a heads-up that I would like to join today's > shore leave to discuss a potential transition of ch-k8s-lbaas into > ALASCA, specifically as part of Tarook. I discussed the issue on 2026-09-11 with Steve and we were in agreement that moving ch-k8s-lbaas into Tarook's governance would be a good move. I've put a more concrete proposal into writing, including some specific work items that would need to be tackled: https://gitlab.com/alasca.cloud/tarook/meta/-/work_items/8 One of the open questions is under what name the project will live on, I hope we don't have to spend too much time on that ;) I'll join the Shore Leave this Friday to discuss this further with the team. Best regards Friedrich

Sept. 21, 2026

Re: Topic for shore leave - future of ch-k8s-lbaas

by Steve Starke

Hi Friedrich, thanks for the heads-up, actually we were considering skipping today's shore leave due to absences. However, let's use the slot to discuss your concerns, since I also feel that the current situation is less than ideal. Best regards Steve On 11.09.26 10:16, Friedrich Zahn via Tarook wrote: > Hi everyone, > > I would like to give you a heads-up that I would like to join today's > shore leave to discuss a potential transition of ch-k8s-lbaas into > ALASCA, specifically as part of Tarook. Please let me know if the > meeting happens to not take place today or if there is no room on the > agenda, it's not too urgent. > > For everyone not familiar with the topic, some background: > ch-k8s-lbaas[0] is used by Tarook to provide a quick and simple > solution for ingress traffic, and advertised as a regular, stable > feature[1]. > > Unfortunately, the code base provenance is currently rather confusing, > there are 3 repos/forks (partially diverged) on GitHub/GitLab and 2 > registries serving images with no clear relationship between each > other. Tarook itself is using a mix of upstream sources, GitLab.com > for images and GitHub for binary artifacts. > Finally, a PR[2] I opened in April has not yet seen any maintainer > reaction, which I take as symptomatic for a general lack of upstream > activity, the last commit to main and release happened more than 2 > years ago. > > To ensure ALASCA's claim of delivering stable and operational > solutions we would like to see this tool under reliable governance, > the FOCIS team is happy to help with the transition efforts if the > Tarook team decides to proceed along that path. > > Best regards, > Friedrich > > [0]: https://github.com/cloudandheat/ch-k8s-lbaas > [1]: > https://docs.tarook.cloud/release/v14.0/user/explanation/services/ch-k8s-lb… > [2]: https://github.com/cloudandheat/ch-k8s-lbaas/pull/59 > > _______________________________________________ > Tarook mailing list -- tarook(a)lists.alasca.cloud > To unsubscribe send an email to tarook-leave(a)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(a)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

Sept. 11, 2026

Topic for shore leave - future of ch-k8s-lbaas

by Friedrich Zahn

Hi everyone, I would like to give you a heads-up that I would like to join today's shore leave to discuss a potential transition of ch-k8s-lbaas into ALASCA, specifically as part of Tarook. Please let me know if the meeting happens to not take place today or if there is no room on the agenda, it's not too urgent. For everyone not familiar with the topic, some background: ch-k8s-lbaas[0] is used by Tarook to provide a quick and simple solution for ingress traffic, and advertised as a regular, stable feature[1]. Unfortunately, the code base provenance is currently rather confusing, there are 3 repos/forks (partially diverged) on GitHub/GitLab and 2 registries serving images with no clear relationship between each other. Tarook itself is using a mix of upstream sources, GitLab.com for images and GitHub for binary artifacts. Finally, a PR[2] I opened in April has not yet seen any maintainer reaction, which I take as symptomatic for a general lack of upstream activity, the last commit to main and release happened more than 2 years ago. To ensure ALASCA's claim of delivering stable and operational solutions we would like to see this tool under reliable governance, the FOCIS team is happy to help with the transition efforts if the Tarook team decides to proceed along that path. Best regards, Friedrich [0]: https://github.com/cloudandheat/ch-k8s-lbaas [1]: https://docs.tarook.cloud/release/v14.0/user/explanation/services/ch-k8s-lb… [2]: https://github.com/cloudandheat/ch-k8s-lbaas/pull/59

Sept. 11, 2026