Hi, I believe it makes sense to mark the project as inactive or even retired. In the past cycles Kuryr was maintained by a team of Red Hat developers, because kuryr-kubernetes was offered as a CNI choice for OpenShift. Observing customers' issues with Kuryr and Neutron scalability, and seeing that other non-OpenStack-native CNI's are starting to offer a comparable networking performance, we've decided to deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got removed in 4.15 (released recently). This means that the incentive to keep the project alive is gone and it's a wise decision to put it as inactive. However we need to make sure this won't affect Zun. To my knowledge Zun is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay with moving kuryr-libnetwork into Zun's control as they are probably the only active users of that code. Thanks, Michał On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote:
Hello Everyone,
Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945
If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945.
[1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inacti...
-gmann