kmesh-net
[LFX-2025-Sep-Nov] Kmesh Orion replace waypopint
What would you like to be added:
- Testing of Orion's key functions for waypoints such as communication with control surfaces, authorization policy, etc.
- If there is missing functionality, it needs to be adapted and supplemented.
- Provides a way to install Orion via Kmeshctl.
Why is this needed: Kmesh, as a high-performance service mesh data plane, does have a performance advantage when compared to other service mesh data planes. However, in high-concurrency scenarios with application-layer protocols such as HTTP, it is held back by the waypoint. Therefore, we developed Orion to replace the waypoint. However, there is still some adaptive functionality development and testing that needs to be done before we can replace it.
Assign it to me first. If anyone else is interested, I can unassign it.
Hi @LiZhenCheng9527. the project looks very interesting to me. Could you guide me on where can I get more understanding of Kmesh as well if there is any official communication medium do let me know. Would certainly like to explore more and collaborate!! Thanks.
Sorry. I will assign this issue to final one selected by LFX membership.
Happy to see some many people interested in this project. In order to select the most suitable person for this project. I will post some tasks here. The one who perform best will be selected.
First task:
We already have a Dockerfile in orion (https://github.com/kmesh-net/orion/blob/main/docker/Dockerfile), but it has some issues and can't run directly. I hope some one can make a PR that fix the issues of the Dockerfile and add a section in Quick Start of README to guide users on how to run orion with docker.
@YaoZengzeng "I’ll work on fixing the Dockerfile and adding Docker instructions to the README. Will submit a PR soon!"
Hi @YaoZengzeng, Thanks for the opportunity! I’ve gone ahead and created a PR #5 that addresses the Dockerfile issues and adds a Docker section in the Quick Start of the README.
Looking forward to your feedback! Let me know if any improvements are needed.
@Wolf-06 Of course, I will post more tasks in the future. You can work on them if no one has posted a PR. If someone has already made a PR, maybe you could review it first :)
@YaoZengzeng I would like to raise a PR for the same if its allowed. Or else you can notify whenever a new task appears.
@YaoZengzeng I would like to raise a PR for the same if its allowed. Or else you can notify whenever a new task appears.
It'd be better not to raise duplicate PR. You can review existing PR if you want. And I'll post new tasks later :)
New task https://github.com/kmesh-net/orion/issues/8, take if interested.
By the way, what really matter is getting code merged. Submitting a lot of PR but not merged will make no sense :)
New tasks will be posted in issues of orion: https://github.com/kmesh-net/orion/issues . Anyone interested can assign issue to themseleves.
Dear @YaoZengzeng ,
I want to express my interest in being a mentee in this project. I have a relatively new background in Rust development, with a project published on my GitHub. Besides, my projects and experiences are mostly filled with ML engineering and software engineering tasks in various tech stack, such as Modern C++ (C++17), CMake, python, go, bash.
I’ve completed the pretest and posted it in my GitHub repo and have reviewed the project’s requirements. I already have a clear understanding of the new code objectives for this mentorship and how they align with the project’s goals.
Looking forward to the possibility of working with you.
Best regards,
