docs: add Kmesh v1.2.0 release blog

[arnavgogia20]

Summary

This PR adds the Kmesh v1.2.0 release blog to the website, following the structure and style of the previous v1.1.0 release blog.

Details

• Covers key features and enhancements introduced in v1.2.0
• Highlights stability improvements, DNS proxy, IPsec, dual-engine enhancements, and Istio 1.26 compatibility
• Includes critical fixes and contributor acknowledgments
• Adds diagrams/placeholders where relevant for better readability

Related Issue

Closes #263

[netlify]

✅ Deploy Preview for kmesh-net ready!

Name	Link
🔨 Latest commit	37cfd8b
🔍 Latest deploy log	https://app.netlify.com/projects/kmesh-net/deploys/69620930aa75c10008b501b7
😎 Deploy Preview	https://deploy-preview-264--kmesh-net.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kmesh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nlgwcy for approval. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[kmesh-bot]

Welcome @arnavgogia20! It looks like this is your first PR to kmesh-net/website 🎉

[gemini-code-assist]

Summary of Changes

Hello @arnavgogia20, I'm Gemini Code Assist¹! 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 introduces the official release blog post for Kmesh v1.2.0, detailing significant advancements in reliability, security, and ecosystem compatibility. It highlights new features like enhanced DNS proxying, improved IPsec support, and expanded service integration, alongside critical bug fixes and stability improvements, all aimed at bolstering Kmesh's readiness for production environments.

Highlights

• Kmesh v1.2.0 Release Blog: Introduced the official release blog post for Kmesh v1.2.0, detailing all new features, enhancements, and bug fixes.
• DNS & dnsProxy Enhancements: Added dnsProxy capabilities for intercepting DNS resolution requests and improved hostname resolution reliability with a dedicated domain-to-IP mapping table.
• IPsec Support Strengthened: Resolved critical interoperability issues between Kmesh-managed and unmanaged nodes, and integrated secret management for encryption keys into the kmeshctl tool.
• Expanded ServiceEntry Support: Fully expanded ServiceEntry support to seamlessly integrate a wider range of external and non-Kubernetes-native services.
• Zero-Downtime Upgrade (Alpha): Introduced an alpha feature allowing Kmesh daemon upgrades without disrupting established connections when BPF map structures remain unchanged.
• Dual-Engine Mode Enhancements: Added circuit breaking and local rate limiting capabilities to dual-engine mode for more granular control over service-to-service communication.
• Istio Compatibility Updates: Ensured full compatibility with Istio 1.26 and deprecated support for Istio 1.23 in CI testing.
• Critical Bug Fixes & Stability: Implemented numerous fixes across IPsec, kmeshctl workflows, eBPF, CI/dependencies, and Istio adaptation to enhance overall stability and reliability.
• Contributor Acknowledgments: Acknowledged both new and existing contributors who made valuable contributions to the Kmesh v1.2.0 release.

🧠 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.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds the release blog for Kmesh v1.2.0. The blog post is well-written and provides a good overview of the new features and improvements. I've made a few suggestions to improve formatting, readability, and to correct a few minor issues. Specifically, I've suggested making PR numbers clickable links, improving the formatting of the contributor list, and correcting the release link at the end of the post. These changes will enhance the user experience and ensure the accuracy of the information provided.

[kmesh-bot]

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:

• e016d3e Update blog/kmesh-1.2-release/index.md
• 6ec8090 Update blog/kmesh-1.2-release/index.md
• f9f115b Update blog/kmesh-1.2-release/index.md
• b9ce235 Update blog/kmesh-1.2-release/index.md
• 6eb3284 Update blog/kmesh-1.2-release/index.md
• 103eb10 Update blog/kmesh-1.2-release/index.md
• 955080c Update blog/kmesh-1.2-release/index.md
• e97fe8c Update blog/kmesh-1.2-release/index.md
• 37cfd8b Update blog/kmesh-1.2-release/index.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.

[arnavgogia20]

Hiii @hzxuzhonghu @YaoZengzeng @yashisrani , can you pls review my PR and let me know if it works well enough or ill have to make some changes

[yashisrani]

@arnavgogia20 please add some diagrams in blog.. and solve this DCO issue by using git commit -m "" -s command.