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
