[WIP] Add KubeEdge 2026 roadmap

[Shelley-BaoYue]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, 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 comprehensively updates the KubeEdge project roadmap, transitioning from a 2024 to a 2026 feature plan. The changes reflect a strategic re-evaluation of priorities across various Special Interest Groups, introducing new initiatives, streamlining existing ones, and reorganizing content to better align with the project's future direction and evolving landscape of edge computing.

Highlights

• Roadmap Year Update: The KubeEdge project roadmap has been updated from outlining 2024 features to detailing plans for 2026, reflecting a forward-looking strategic shift.
• Strategic Revisions Across SIGs: Significant revisions were made to the feature plans for multiple Special Interest Groups (SIGs), including Node, Device-IOT, Security, Networking, AI, Robotics, Testing, Cluster-Lifecycle, UI, and Experience, aligning them with new project priorities.
• New Documentation Section: A dedicated 'Documentation' section has been introduced, outlining plans for multi-language support using AI tools and content restructuring.
• Enhanced AI and Cluster-Lifecycle Focus: The SIG AI section was completely revamped to include AI Conformance support and hands-on examples for edge model deployment, while SIG Cluster-Lifecycle received new enhancements for remote maintenance, CloudCore HA, and API stability.

🧠 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

• roadmap.md
  • Updated the roadmap's target year from 2024 to 2026.
  • Revised SIG Node features, adding support for Mac OS/RTOS, edge clusters, and runtimeclass while removing several older items.
  • Updated SIG Device-IOT plans to include batch device management and the establishment of a multi-language mapper-framework repository.
  • Streamlined SIG Security by removing specific items related to SLSA/CodeQL and certificate capabilities.
  • Removed the standalone 'Stability' section, integrating its relevant items into SIG Cluster-Lifecycle.
  • Refined SIG Networking by removing detailed large-scale optimization points.
  • Completely revamped SIG AI, introducing goals for AI Conformance support and hands-on examples for edge model deployment.
  • Updated SIG Robotics to focus on providing examples and solutions for robotics scenarios.
  • Revised SIG Testing to include AI-generated unit and E2E tests and optimization for integration testing.
  • Updated SIG Cluster-Lifecycle with enhancements for remote maintenance, CloudCore HA, and stability improvements for the Edge Kube-API interface and logs/exec features.
  • Expanded UI plans to include a new tutorial page on the official website, container deployment for the Dashboard, and general Dashboard enhancement iterations.
  • Added a new 'Documentation' section, outlining plans for multi-language documentation maintenance with AI tools and content restructuring.
  • Updated SIG Experience to focus on integrating the example repository with the KubeEdge core in the CI/CD pipeline.

Activity

• No activity has been recorded for this pull request 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. ↩

[gemini-code-assist]

Code Review

The pull request updates the KubeEdge roadmap from 2024 to 2026, involving extensive revisions across various SIG sections, including the removal of the "Stability" section and the addition of a new "Documentation" section. Review comments suggest correcting a typo from "ServichMesh" to "ServiceMesh", ensuring consistent formatting by removing a trailing period from a list item, and adding a missing newline character at the end of the file.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

There seems to be a typo here. ServichMesh should probably be ServiceMesh.

Suggested change

	- ServichMesh
	- ServiceMesh

[gemini-code-assist]

This list item ends with a period, which is inconsistent with the other items in the roadmap. For consistency, it's better to remove the trailing period.

Suggested change

	- Restructure and refactor the contents.
	- Restructure and refactor the contents

[gemini-code-assist]

It's a good practice for files to end with a newline character. This file is missing one. Please add a newline at the end of the file.

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fujitatomoya
To complete the pull request process, please assign shelley-baoyue after the PR has been reviewed.
You can assign the PR to them by writing /assign @shelley-baoyue in a comment when ready.

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

[Shelley-BaoYue]

@MooreZheng Please provide more for SIG AI