Proposing roadmap of 2026

[RainbowMango]

What type of PR is this?

/kind documentation

What this PR does / why we need it:
This pull request updates Karmada's feature and development plans for 2026. The update introduces several new feature areas and clarifies ongoing efforts, providing more detail and specific tracking references for upcoming work.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

[karmada-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 carmark for approval. For more information see the 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

[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 updates Karmada's official roadmap document, shifting its focus to the strategic feature and development plans for 2026. It introduces several new key initiatives aimed at enhancing scheduling, resource management, and API maturity, providing a clearer vision for the project's future direction and encouraging community engagement.

Highlights

• Roadmap Year Update: The document's focus has been shifted from the 2025 feature plan to the 2026 feature plan.
• Application Priority and Preemption: Introduced plans to add preemption capabilities, building on 2025's priority scheduling, with a reference to a detailed proposal.
• Multi-cluster Queue Management: Added a new initiative to provide queueing for managing multi-tenant AI training and batch job workloads across clusters.
• Precise Cluster Resource-Aware Scheduling: Included a new feature to pre-deduct required resources in member clusters before workload synchronization to prevent overload, linking to a tracking issue.
• Core API Promotion: Outlined the plan to promote core APIs (PropagationPolicy, OverridePolicy) to beta, incorporating adjustments based on multi-year usage.
• Extended Cluster Affinities: Described the evolution of cluster affinity capabilities, referencing both original design and a new extension proposal.
• UI Development Description: The description for UI development was generalized to reflect ongoing iteration rather than a specific 2025 release.

Changelog

• ROADMAP.md
  • Updated the roadmap's target year from 2025 to 2026.
  • Added new sections detailing future plans for Application Priority and Preemption, Multi-cluster Queue Management, Precise Cluster Resource-Aware Scheduling, Core API Promotion to Beta, and Extended Cluster Affinities.
  • Revised the description of UI development to emphasize continuous iteration and user feedback.

Activity

• No specific activity (comments, reviews, or progress updates) was provided for this pull request.

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 successfully updates the Karmada roadmap for 2026, replacing the previous year's plan with a more detailed and structured outline of new features and ongoing efforts. The changes enhance clarity and provide valuable tracking references for the community. I have one minor formatting suggestion to improve the document's consistency.

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

[gemini-code-assist]

There is a trailing whitespace in this header. It should be removed for better formatting and consistency.

Suggested change

	## Others
	## Others

[XiShanYongYe-Chang]

Thanks
/lgtm