docs:add beginner guide to service mesh and update diagrams - #334
docs:add beginner guide to service mesh and update diagrams#334devGPP23 wants to merge 1 commit into
Conversation
✅ Deploy Preview for kmesh-net ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @devGPP23! It looks like this is your first PR to kmesh-net/website 🎉 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new beginner-friendly blog post titled "Kmesh: The Ultimate Guide to Service Mesh for Beginners", updates the authors' profiles, and links the post in the README. The review feedback focuses on polishing the blog post by correcting minor grammatical errors and ensuring formatting consistency across list items.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| *"Who is making sure all of this communication works properly?"* | ||
|
|
||
| This growing complexity makes managing your microservices **painful**. Several solutions were proposed for that. |
There was a problem hiding this comment.
The sentence "Several solutions were proposed for that." can be phrased more naturally using the present perfect tense.
| This growing complexity makes managing your microservices **painful**. Several solutions were proposed for that. | |
| This growing complexity makes managing your microservices **painful**. Several solutions have been proposed to address this. |
|
|
||
| Why was this a breakthrough? | ||
|
|
||
| - Order Service in Java, Payment Service in Go? Doesn't matter — the same Envoy proxy handles networking for all of them. |
There was a problem hiding this comment.
To maintain consistency with the other items in this list (which all start with a bolded term), we should format this item with a bolded prefix.
| - Order Service in Java, Payment Service in Go? Doesn't matter — the same Envoy proxy handles networking for all of them. | |
| - **Language independence:** Order Service in Java, Payment Service in Go? Doesn't matter — the same Envoy proxy handles networking for all of them. |
|
|
||
| ### How Does Kmesh Know Where to Route Traffic? | ||
|
|
||
| Kmesh doesn't reinvent any of the control plane logic. If you're already using Istio, defining your traffic rules is exactly the same way. Same YAML files, same routing policies, same canary deployments. |
There was a problem hiding this comment.
The phrase "defining your traffic rules is exactly the same way" is grammatically awkward. It should be "defining your traffic rules works exactly the same way" or "defining your traffic rules is done in exactly the same way".
| Kmesh doesn't reinvent any of the control plane logic. If you're already using Istio, defining your traffic rules is exactly the same way. Same YAML files, same routing policies, same canary deployments. | |
| Kmesh doesn't reinvent any of the control plane logic. If you're already using Istio, defining your traffic rules works exactly the same way. Same YAML files, same routing policies, same canary deployments. |
There was a problem hiding this comment.
Pull request overview
Adds a new beginner-oriented Kmesh blog post and wires it into the site’s author metadata and main README for discoverability, while also introducing updated English-only diagrams referenced by the post.
Changes:
- Added a new blog post: “Kmesh: The Ultimate Guide to Service Mesh for Beginners”.
- Added/updated blog author entries (including
devGPP23) in both global and zh i18n author lists. - Linked the new guide from
README.md.
Reviewed changes
Copilot reviewed 4 out of 21 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Adds a prominent link to the new beginner guide from the repo entrypoint. |
| i18n/zh/docusaurus-plugin-content-blog/authors.yml | Adds the new author entry for the blog (zh i18n metadata). |
| blog/kmesh-service-mesh-explained/index.md | Introduces the new beginner guide content and references updated English diagrams. |
| blog/authors.yml | Updates author metadata (adds devGPP23, updates jayesh9747 avatar URL). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1,338 @@ | |||
| --- | |||
| title: "Kmesh: The Ultimate Guide to Service Mesh for Beginners" | |||
| summary: "A beginner-friendly guide explaining concept behind service meshes, why traditional meshes are slow, how eBPF works, and how Kmesh uses kernel-native traffic governance to deliver near-zero latency overhead." | |||
| date: 2025-07-19T12:00:00+05:30 | ||
| last_update: | ||
| date: 2025-07-19T12:00:00+05:30 |
027b6c2 to
aaef9c7
Compare
| - What problem Kmesh is solving (and why that problem matters) | ||
| - How the current solutions work (and why they're slow) | ||
| - What Kmesh does differently (and why it's faster) | ||
| - How all the pieces fit together | ||
|
|
||
|
|
||
| ## What is a Service Mesh and Why Does It Exist? |
|
|
||
| All that bouncing means data gets copied back and forth between **user space** and **kernel space** multiple times. It means extra TCP connections get established. It means more CPU cycles, more memory, and more latency. | ||
|
|
||
| According to Istio's own benchmarks, the sidecar proxy adds approximately **2.65 milliseconds** of latency per hop. Suddenly, you're looking at an extra 15-25ms of pure overhead that has nothing to do with your business logic. |
|
|
||
|  | ||
|
|
||
|  |
|
|
||
| As the diagram shows, a lightweight component called **kmesh-daemon** runs on each node in your cluster. Its job is: | ||
|
|
||
| 1. **Listening** to Istio's control plane for routing rules via **xDS** (a standard protocol that Istio uses to push configuration to its data plane) — Envoy and Kmesh too use xDS. |
d493856 to
475ce46
Compare
| - What Kmesh does differently (and why it's faster) | ||
| - How all the pieces fit together | ||
|
|
||
| <!-- truncate--> |
|
|
||
| Why was this a breakthrough? | ||
|
|
||
| - **Language independence:**Order Service in Java, Payment Service in Go? Doesn't matter — the same Envoy proxy handles networking for all of them. |
475ce46 to
398d243
Compare
Signed-off-by: devGP7 <gauravpatil232005@gmail.com>
398d243 to
82ad715
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 21 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
blog/kmesh-service-mesh-explained/index.md:24
- The blog excerpt truncation marker is formatted differently from the rest of the blog posts (
<!-- truncate -->). With the current<!-- truncate-->(and indentation), Docusaurus may not detect it, causing the full post to appear on the blog list page instead of an excerpt.
<!-- truncate-->
|
/cc @LiZhenCheng9527 Please review and give feedback whenever you have chance to review |
Currently, there isn't a beginner-friendly guide explaining the core concepts of service meshes, eBPF, and how Kmesh operates compared to traditional sidecar models. Also, a few of the existing architecture diagrams contain Chinese text, making them difficult for English-speaking users to fully grasp.
As discussed with @LiZhenCheng9527 on Slack, I've put together a blog post to serve as a beginner's guide to Kmesh!
istio-perf-analysis.pngandebpf-sockmap-pods.pngdiagrams to be entirely in English.README.mdfor better visibility.Fixes #333