-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HEALTH]: OpenELB #1542
Comments
@renyunkang @chaunceyjiang @FeynmanZhou @zheng1 @duanjiong @magicsong @patrick-luoyu @AnuragThePathak @liangyuanpeng @amal-thundiyil |
Notes:
|
Another inactivity indicator; they never completed onboarding: cncf/sandbox#182 |
We sincerely appreciate the community’s ongoing attention and support for the OpenELB project. We deeply apologize for the recent decline in project activity, which stemmed primarily from internal resource reallocations and insufficient community engagement, leading to delays in planned developments. However, OpenELB remains a critical tool for Kubernetes load balancing, and we are fully committed to revitalizing the project and delivering sustained improvements. Future Plans & Commitments:
We recognize that the project’s vitality hinges on community trust and participation. Moving forward, we will provide regular progress updates and rebuild an active, collaborative environment through transparent communication. Thank you for your understanding and continued support. OpenELB is dedicated to empowering seamless Kubernetes load balancing with renewed openness and innovation. |
Project name
OpenELB
Concern
There has been minimal activity over the past 90 days, and decreased activity before that.
No commits since October of last year
Additional information can be seen on OpenELB's LFX insights dashboard
Prior engagement
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: