blog: add Kmesh v1.2.0 blog post#278
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 @MeloveGupta! 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 author to the blog configuration and introduces a comprehensive blog post announcing the release of Kmesh v1.2.0, which includes features such as DNS proxying, enhanced IPsec, and zero-downtime upgrades. The review feedback provides several suggestions to improve the blog post's grammar, punctuation, and terminology for better readability, and notes a missing newline at the end of a YAML file.
| name: Melove Gupta | ||
| title: Kmesh Contributor | ||
| url: https://github.com/MeloveGupta | ||
| image_url: https://avatars.githubusercontent.com/u/119809561?v=4 No newline at end of file |
There was a problem hiding this comment.
The file should end with a newline character to adhere to standard POSIX formatting and ensure compatibility with various text processing tools.
image_url: https://avatars.githubusercontent.com/u/119809561?v=4
|
|
||
| This is the feature that makes half of everything else in this release possible. | ||
|
|
||
| Before v1.2.0, Kmesh had no real handle on DNS. It worked alongside the cluster's DNS resolution flow but couldn't intercept or influence it. That ceiling showed up everywhere in ServiceEntry limitations, in dual-engine mode constraints, in the gap between what Kmesh could theoretically govern and what it could actually reach. |
There was a problem hiding this comment.
This sentence is missing a conjunction or proper punctuation for the list. Adding a colon and 'and' improves readability and flow.
| Before v1.2.0, Kmesh had no real handle on DNS. It worked alongside the cluster's DNS resolution flow but couldn't intercept or influence it. That ceiling showed up everywhere in ServiceEntry limitations, in dual-engine mode constraints, in the gap between what Kmesh could theoretically govern and what it could actually reach. | |
| Before v1.2.0, Kmesh had no real handle on DNS. It worked alongside the cluster's DNS resolution flow but couldn't intercept or influence it. That ceiling showed up everywhere: in ServiceEntry limitations, in dual-engine mode constraints, and in the gap between what Kmesh could theoretically govern and what it could actually reach. |
|
|
||
|  | ||
|
|
||
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the PR that tears it down. |
There was a problem hiding this comment.
In a blog post, it is more appropriate to refer to the 'feature' or 'release' rather than the 'PR'.
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the PR that tears it down. | |
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the feature that tears it down. |
|
|
||
| ### Zero-Downtime Upgrade Capability | ||
|
|
||
| This one has a caveat, it is currently alpha. But the problem it solves is real and worth calling out. |
There was a problem hiding this comment.
This is a comma splice. Using a colon to separate these independent clauses is more grammatically correct as the second clause explains the first.
| This one has a caveat, it is currently alpha. But the problem it solves is real and worth calling out. | |
| This one has a caveat: it is currently alpha. But the problem it solves is real and worth calling out. |
|
|
||
| This one has a caveat, it is currently alpha. But the problem it solves is real and worth calling out. | ||
|
|
||
| Upgrading the Kmesh daemon used to mean accepting connection disruption. In v0.5.0, we made restarts non-disruptive. v1.2.0 extends that guarantee to the full upgrade workflow: as long as BPF map structures have not changed between versions, upgrading the daemon will not drop existing connections. For a data plane component that sits directly in the path of all service to service traffic, this matters enormously. |
There was a problem hiding this comment.
The phrase 'service to service' should be hyphenated when used as a compound adjective modifying 'traffic'.
| Upgrading the Kmesh daemon used to mean accepting connection disruption. In v0.5.0, we made restarts non-disruptive. v1.2.0 extends that guarantee to the full upgrade workflow: as long as BPF map structures have not changed between versions, upgrading the daemon will not drop existing connections. For a data plane component that sits directly in the path of all service to service traffic, this matters enormously. | |
| Upgrading the Kmesh daemon used to mean accepting connection disruption. In v0.5.0, we made restarts non-disruptive. v1.2.0 extends that guarantee to the full upgrade workflow: as long as BPF map structures have not changed between versions, upgrading the daemon will not drop existing connections. For a data plane component that sits directly in the path of all service-to-service traffic, this matters enormously. |
There was a problem hiding this comment.
Pull request overview
Adds a new Docusaurus blog post announcing the Kmesh v1.2.0 release (mirroring the v1.1.0 post structure) and registers the new author so the post renders correctly in both default and zh locales.
Changes:
- Added
blog/kmesh-1.2-release/index.mdwith release highlights and embedded flowchart images. - Added
MeloveGuptaauthor metadata to blog author registries (default +i18n/zh).
Reviewed changes
Copilot reviewed 3 out of 9 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| i18n/zh/docusaurus-plugin-content-blog/authors.yml | Adds MeloveGupta author entry for the zh blog locale. |
| blog/kmesh-1.2-release/index.md | New Kmesh v1.2.0 release blog post content and image references. |
| blog/authors.yml | Adds MeloveGupta author entry for the default blog locale. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
|  | ||
|
|
||
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the PR that tears it down. |
There was a problem hiding this comment.
This release announcement refers to “this is the PR that tears it down”, but this page is a blog post about the v1.2.0 release. Consider changing “PR” to “release” (or similar) to avoid confusing readers about what is being referenced.
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the PR that tears it down. | |
| v1.2.0 adds a proper DNS proxy. Kmesh now intercepts DNS resolution requests for services it manages and maintains its own internal domain-to-address mapping table. This means Kmesh knows what's being resolved, when, and can act on it. If you've ever hit a wall with Kmesh and external service management, this is the release that tears it down. |
Signed-off-by: Melove <melovegupta0406@gmail.com>
MeloveGupta
force-pushed
the
blog/kmesh-1.2-release
branch
from
298398b to
89ca19c
Compare
Signed-off-by: Melove <melovegupta0406@gmail.com>
MeloveGupta
force-pushed
the
blog/kmesh-1.2-release
branch
from
f5d2545 to
a22de88
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 9 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | | | | | | ||
| | ------------ | ---------------- | ---------- | ------------- | | ||
| | @Flying-Tom | @zrggw | @yashisrani| @AkarshSahlot | | ||
| | @mdimado | @Vinnu124 | @wxnzb | @072020127 | | ||
| | @xiaojiangao123 | @Kuromesi | @YaoZengzeng | @LiZhenCheng9527 | |
There was a problem hiding this comment.
The contributor list table uses || at the start of each row, which breaks standard Markdown table syntax and will likely render with an extra empty column or not as intended. Please switch to the normal | col | col | ... | format (single leading pipe) and ensure the header/separator rows match the number of columns.
This PR adds the Kmesh v1.2.0 blog post to the website, following the structure of the previous v1.1.0 blog post.
I've covered the main features in the release v1.2.0
I've also added flowchart images.
Closes #263