Repository navigation
[Tech Review]: Higress #2266
Description
Project name
Higress
Project link
https://github.com/higress-group/higress
Due diligence link
No response
Project contact information
- Yuanxiao Zhao: @EndlessSeeker
- Tianyi Zhang: @johnlanni
- Yiquan Dong: @CH3CHO
Additional information
Higress is a CNCF Sandbox project preparing for an Incubation application and is requesting an independent General Technical Review from the CNCF Project Reviews SubProject.
This request supersedes #2262, which was created through the GitHub CLI and did not receive the standard Project Reviews labels.
Review materials:
- Project-wide community and governance repository:
https://github.com/higress-group/community - Project-maintained General Technical Review:
https://github.com/higress-group/community/blob/main/docs/cncf/general-technical-review.md - Incubation application working draft:
https://github.com/higress-group/community/blob/main/docs/cncf/incubation-application.md - Governance Review working copy:
https://github.com/higress-group/community/blob/main/docs/cncf/governance-review.md - Security Self-Assessment:
https://github.com/higress-group/community/blob/main/docs/cncf/security-self-assessment.md - Architecture documentation:
https://github.com/higress-group/higress/blob/main/docs/architecture.md - Public roadmap:
https://github.com/higress-group/community/blob/main/ROADMAP.md - Public adopters:
https://github.com/higress-group/community/blob/main/ADOPTERS.md - Maintainers:
https://github.com/higress-group/community/blob/main/MAINTAINERS.md - Public community meetings:
https://github.com/higress-group/community/blob/main/MEETINGS.md - OpenSSF Best Practices badge:
https://www.bestpractices.dev/projects/12667 - Sandbox application and successful vote:
[Sandbox] Higress sandbox#445 - Completed Sandbox onboarding:
[PROJECT ONBOARDING] Higress sandbox#481
The project-maintained General Technical Review was approved in higress-group/higress#4177 and subsequently refreshed as part of the project's Incubation preparation. Project-wide review materials are now maintained in higress-group/community.
We welcome an independent reviewer assessment and will address findings through public issues and pull requests. We request coordination of the final dated review snapshot under:
projects/higress/tech-review/YYYY-MM-DD.md
Activity
elang2 commentedon Aug 10, 2026
I'd like to contribute an independent technical review. My recent area of interest in OSS has been AI cost observability, which started when I began looking into how agents rack up inference costs without standard ways to measure or cap them. That led to active contributions across the protocol stack:
The areas I can specifically assess: whether the ai-statistics plugin's Prometheus metrics (token counting, TTFT, multi-dimensional labels) will hit cardinality problems at high request volumes. The MCP gateway's tool-routing architecture and whether tool invocations are traceable end-to-end through the routing layer. And the WASM plugin isolation model for streaming workloads, particularly the documented CPU exhaustion in Issue #4034 and how that interacts with long-lived SSE connections (which are the norm for AI use cases).
Happy to follow whatever review template the SubProject uses.
EndlessSeeker commentedon Aug 12, 2026
Thanks @elang2 — really appreciate you volunteering. The areas you called out are very relevant to Higress, especially AI observability, MCP routing, and WASM behavior in streaming workloads.
The current GTR and supporting materials are linked in the issue. We’re happy to answer questions or point you to the relevant code and docs as you go.
@angellk @brandtkeller, could you help confirm whether @elang2 can take this review, and what the next step should be for the assignment and final dated snapshot? Thanks!
brandtkeller commentedon Aug 13, 2026
I would encourage @elang2 to join a future Project Reviews Meeting if interested in helping with the current queue and Due Diligence priorities.
Given the project maintains a Tech Review already this should not be too significant of a process once prioritized.
elang2 commentedon Aug 14, 2026
Thanks @EndlessSeeker, glad those areas line up. I'll go through the GTR and linked materials. Will probably have questions once I'm deeper into the WASM plugin lifecycle for streaming and the MCP tool-routing internals, so I'll take you up on that offer.
@brandtkeller, sounds good. How do I get on the agenda for a Project Reviews Meeting? Happy to join the next one that works.
EndlessSeeker commentedon Aug 31, 2026
Hi @brandtkeller — following up on the technical review. @elang2 has volunteered and is ready to review the linked GTR. Could you confirm whether they can be formally assigned, and whether the Higress maintainers should join a Project Reviews meeting at this stage? Happy to provide anything else needed. Thanks!
EndlessSeeker commentedon Oct 12, 2026
The Higress technical self-assessment is now submitted in #2324 so reviewers can comment directly on the document. It supports our incubation application #2291 and is awaiting CNCF review.