Skip to content

Comments

docs: Add architecture diagram and reorganize README structure#159

Merged
dawid-nowak merged 12 commits intokmesh-net:mainfrom
JameelHao:main
Feb 16, 2026
Merged

docs: Add architecture diagram and reorganize README structure#159
dawid-nowak merged 12 commits intokmesh-net:mainfrom
JameelHao:main

Conversation

@JameelHao
Copy link
Contributor

Summary

This PR adds a comprehensive architecture section to the README with a professional diagram, and reorganizes the documentation structure for better readability.

Changes

  • ✨ Add Architecture section with high-quality diagram (draw.io style)
  • 📊 Add detailed Core Components and Key Design Principles descriptions
  • 📝 Reorganize README structure: Introduction → Architecture → Quick Start
  • 📜 Add CODE_OF_CONDUCT.md for community guidelines
  • 🎨 Format improvements and consistency fixes

Files Changed

  • README.md - Major update with architecture section (+55/-42 lines)
  • docs/pics/architecture/orion_architecture.png - New architecture diagram (447 KB, 300 DPI)
  • CODE_OF_CONDUCT.md - Community code of conduct

Architecture Diagram Features

  • Draw.io style with solid arrow heads
  • High-resolution (300 DPI) for documentation quality
  • Clear component hierarchy: Control Plane → xDS → Core Engine → Transport → Observability → Upstream
  • Professional color scheme and layout

Impact

  • Improves documentation clarity for new users and contributors
  • Provides visual overview of system architecture
  • Better aligns with professional open source project standards

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @JameelHao, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the project's documentation by introducing a comprehensive architecture section, complete with a professional diagram and detailed explanations of core components and design principles. It also reorganizes the main README.md for better flow and clarity, and establishes community guidelines by adding a CODE_OF_CONDUCT.md file. These changes aim to improve onboarding for new users and contributors and elevate the project's overall professionalism.

Highlights

  • Architecture Diagram: A new, high-quality architecture diagram has been added to the README.md to visually represent the system's structure.
  • README Reorganization: The README.md has been restructured to improve readability, moving from an "Introduction" -> "Architecture" -> "Quick Start" flow.
  • Core Components & Design Principles: Detailed descriptions of Orion Proxy's core components and key design principles are now included in the README.md.
  • Code of Conduct: A CODE_OF_CONDUCT.md file has been added, adopting the CNCF Code of Conduct for community guidelines.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • CODE_OF_CONDUCT.md
    • Added a new file to establish community guidelines, referencing the CNCF Code of Conduct.
  • README.md
    • Introduced a new "Architecture" section, including an embedded orion_architecture.png image.
    • Detailed "Core Components" and "Key Design Principles" within the new "Architecture" section.
    • Reordered the main sections to "Introduction", "Architecture", and "Quick Start".
    • Relocated the "CPU/Thread Limit Configuration" section from before "Quick Start" to after the Docker usage instructions.
    • Applied minor formatting improvements and consistency fixes, such as changing "Key features" to "Key Features".
Activity
  • The pull request was created by JameelHao.
  • No human activity (comments, reviews, approvals) has been recorded yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request significantly improves the project's documentation by adding a new CODE_OF_CONDUCT.md file and extensively reorganizing the README.md. The new architecture section, complete with a diagram and detailed descriptions of components and design principles, is a great addition that will help new users and contributors understand the project. The overall structure is now more logical. I've included a couple of minor suggestions to further improve the documentation's presentation and robustness.

- Follow CNCF Code of Conduct
- Consistent with Kmesh community standards
- Same contact email for the Kmesh ecosystem

Signed-off-by: JameelHao <haoxing12311@gmail.com>
- Add comprehensive architecture diagram (ASCII art)
- Document core components and their responsibilities
- Explain xDS integration and data flow
- Highlight key design principles (zero-copy, async, memory safety)
- Follow Kmesh README style

Signed-off-by: JameelHao <haoxing12311@gmail.com>
…ssional diagram

Signed-off-by: JameelHao <haoxing12311@gmail.com>
Signed-off-by: JameelHao <haoxing12311@gmail.com>
Signed-off-by: JameelHao <haoxing12311@gmail.com>
Signed-off-by: JameelHao <haoxing12311@gmail.com>
Signed-off-by: JameelHao <haoxing12311@gmail.com>
…ples

Signed-off-by: JameelHao <haoxing12311@gmail.com>
- Add 4 benchmark charts in a 2x2 table layout
- Show HTTP and HTTPS benchmark results (RPS and Latency)
- Provide visual evidence of 2-4x performance improvement over Envoy

Signed-off-by: JameelHao <haoxing12311@gmail.com>
Keep the documentation focused on core technical strengths. Can be added back in future releases with supporting evidence.

Signed-off-by: JameelHao <haoxing12311@gmail.com>
- Adopt kmesh's lightweight PR template format
- Use /kind labels (bug, feature, enhancement, etc.)
- Add /kind performance for performance-related PRs
- Include release-note section for user-facing changes

Based on: https://github.com/kmesh-net/kmesh/blob/main/.github/PULL_REQUEST_TEMPLATE.md

Signed-off-by: JameelHao <haoxing12311@gmail.com>
@dawid-nowak dawid-nowak self-requested a review February 16, 2026 14:50
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copilot AI review requested due to automatic review settings February 16, 2026 14:51
@kmesh-bot
Copy link
Contributor

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

  • 5040134 Update CODE_OF_CONDUCT.md
Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kmesh-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dawid-nowak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR enhances the Orion Proxy documentation by adding a comprehensive architecture section with a professional diagram and reorganizing the README for better readability. The changes align with professional open source project standards by improving documentation clarity and adding community guidelines.

Changes:

  • Added Architecture section with diagram and detailed descriptions of core components and design principles
  • Added performance benchmark visualization tables to the Key Features section
  • Reorganized README structure to follow Introduction → Architecture → Quick Start flow
  • Added CODE_OF_CONDUCT.md referencing CNCF Code of Conduct
  • Added standardized pull request template for contributors

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File Description
README.md Major restructuring with new architecture section, performance tables, and improved documentation flow
CODE_OF_CONDUCT.md New file establishing community conduct guidelines following CNCF standards
.github/PULL_REQUEST_TEMPLATE.md New standardized template for pull requests with common fields and release notes

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +112 to +116
- name: ORION_CPU_LIMIT
valueFrom:
resourceFieldRef:
resource: limits.cpu
divisor: "1"
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The YAML indentation is inconsistent. This code block mixes 2-space and 4-space indentation, which can cause parsing issues. The Kubernetes YAML standard and other YAML files in this repository use consistent 2-space indentation. The indentation should be:

  • - name: should be indented with 2 spaces
  • valueFrom: should be indented with 4 spaces (2 more than the list item)
  • resourceFieldRef: should be indented with 6 spaces
  • resource: and divisor: should be indented with 8 spaces
Suggested change
- name: ORION_CPU_LIMIT
valueFrom:
resourceFieldRef:
resource: limits.cpu
divisor: "1"
- name: ORION_CPU_LIMIT
valueFrom:
resourceFieldRef:
resource: limits.cpu
divisor: "1"

Copilot uses AI. Check for mistakes.
## Quick Start

**Note:** To control how many CPU cores/threads Orion uses (especially in containers), set the `ORION_CPU_LIMIT` environment variable. In Kubernetes, use the Downward API:
<img src="docs/pics/architecture/orion_architecture.png" alt="Orion Architecture" style="zoom: 80%;" />
Copy link

Copilot AI Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inline HTML styles are not supported by GitHub's markdown renderer and will be ignored. The style="zoom: 80%;" attribute will have no effect on GitHub. Consider removing the style attribute or using an alternative approach such as setting the width attribute or hosting the image at the desired size.

Copilot uses AI. Check for mistakes.
@dawid-nowak dawid-nowak merged commit c64276d into kmesh-net:main Feb 16, 2026
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants