-
Notifications
You must be signed in to change notification settings - Fork 1.6k
add roadmap #16667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
therealmitchconnors
wants to merge
13
commits into
istio:master
Choose a base branch
from
therealmitchconnors:roadmap2025
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+48
−0
Open
add roadmap #16667
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b5ab10b
add roadmap
therealmitchconnors e75497d
Apply suggestions from code review
therealmitchconnors 093fcdc
Fix some spelling, implement feedback
therealmitchconnors 681f0fd
more lints
therealmitchconnors c8b8568
Apply suggestions from code review
therealmitchconnors 31f0ee9
implement suggestions
therealmitchconnors 752da3d
add newline to spelling
therealmitchconnors 93da773
Update content/en/blog/2025/roadmap/index.md
therealmitchconnors 8012add
remove bad .spelling line
therealmitchconnors 9a4e1b7
re-add extensibility to spelling
therealmitchconnors bcee035
add channel to spelling
therealmitchconnors 7370b64
add url to spelling
therealmitchconnors 937a3f3
sort spelling file
therealmitchconnors File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
title: "Istio Roadmap for 2025-2026" | ||
description: Looking ahead to what's next for Istio. | ||
publishdate: 2025-07-20 | ||
attribution: "Mitch Connors, for the Istio TOC" | ||
keywords: [Istio,roadmap,ambient] | ||
--- | ||
|
||
Over the next 12 months, we will focus on improving parity between sidecar mode and ambient mode, providing a supported path for sidecar users to migrate to the ambient data plane when they are ready. We will also revamp our contributor experience, simplifying the process for proposing and implementing new features, and giving recognition to our most valuable contributors. We plan to grow our ecosystem by adding or updating Istio’s integration to various popular cloud native projects and build more case studies for Istio. | ||
|
||
## Looking Back | ||
|
||
Since 2023, the Istio project has been focused on maturity and innovation, solidifying our position as the best service mesh regardless of sidecars or ambient. These efforts included our CNCF graduation in July 2023, the promotion of Telemetry API and Gateway API to Stable in Istio 1.22, and the promotion of ambient mode to Stable in Istio 1.24. As part of Istio ambient mode reaching GA, we have observed more and more users exploring and adopting it, some of the users are net new Istio users, while others are users of Istio sidecars. Some of them ran ambient in production and spoke about their experiences at KubeCon EU in April this year. These efforts have made Istio the service mesh of choice for cloud native developers around the world, and we have been excited to accept first code contributions from 154 people in the past 12 months. | ||
|
||
## 2025 Themes | ||
|
||
### Sidecar to ambient migration | ||
|
||
With the promotion of Istio ambient mode to Stable, the world’s fastest service mesh is also the world’s most efficient, and is now easier to operate than ever. With graduation, we’ve seen a substantial increase in interest, and a corresponding number of requests for a comprehensive migration guide for existing sidecar users. While our previous efforts to stabilize ambient mode have been targeted at new Istio users, it is clear that the time has come to provide an onramp for our existing user base to migrate to ambient mesh. While the technical foundations for this migration have been in place for some time (and some brave users have migrated on their own), we will be making new investments in automated migration testing, tooling to assess your readiness to migrate, and documentation to guide users every step of the way. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't know if I'm comfortable promising automated migration testing. That's a nontrivial lift |
||
|
||
In addition to tests, tooling, and documentation, users migrating between data planes should reasonably expect that the Istio features they know and love will continue to work in their new environment. For this reason, we are investing in closing the most significant functionality gaps between sidecar and ambient mode, specifically by adding support for multi-cluster traffic management and extensibility, which you can read about below. | ||
|
||
As we have stated in previous years, we have no intention of ending support for sidecar mode as long as there are users for it. Migrating to ambient mesh is completely voluntary, and we expect many users will use sidecars for years to come. | ||
|
||
### Multi-cluster ambient mesh | ||
|
||
Multi-cluster traffic management has long been one of the most valued enterprise features of Istio, and we are hard at work to bring this value to ambient mode users in 2025. With a multi-cluster mesh, service outages or anomalies in one cluster can dynamically cause requests to fail over to other clusters, potentially in other regions or clouds. This gives users the ability to run high-availability services in active-active configuration, optimizing compute utilization and traffic costs from a single control plane. Multi-cluster ambient mesh will be available as an Alpha in Istio 1.27, which we plan to release in August. | ||
|
||
### The future of extensibility | ||
|
||
The Istio project has offered several APIs for extensibility since launch, and none of them has been able to mature to Stable. Of those in use today, Envoy Filters are a powerful tool for tweaking internal proxy configuration, and modifying traffic flow, but are very difficult to use, and pose significant risk during upgrades, which can change the filter integrations in ways that cannot always be predicted. WebAssembly (Wasm) emerged in 2019 as a powerful tool for Turing-complete modification of traffic, but community support for Wasm compilers and libraries outside the Istio ecosystem has waned substantially since that time, making it difficult for users to safely and securely use Wasm with Istio. | ||
|
||
As we plan for 2025 and beyond, it is clear that we need a path to a mature extensibility model for users of sidecars and ambient mode alike. We plan to address the most common use cases for extensibility, such as local rate limiting, with first class APIs, reducing the frequency with which users require extensibility. However, we recognize that networks are complex, and there will always be cases our APIs don’t cover, when users need a "break glass" option. The architecture of ambient mode provides some options, such as leveraging the waypoint pattern to accomplish service insertion, adding arbitrary proxies to the network chain, which can then perform arbitrary modifications. Another similar development is [Envoy’s ext-proc filter](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ext_proc/v3/ext_proc.proto), which sends requests to an arbitrary service for modification before forwarding them to their destination. | ||
|
||
With several options on the table for extensibility, who will decide which is best? As always, the final decision lies with you, our users. Please share your thoughts with us about the future of the project in the extensibility channel at [slack.istio.io](https://slack.istio.io/). | ||
|
||
## New and Improved Contributor Experience | ||
|
||
The Istio community is full of many talented contributors whose daily efforts make this project possible, and the list of contributors is always growing! However, like all Open Source projects, we are always in need of new contributors, and we recognize that submitting your first PR to Istio is harder than it should be. In 2025, we aim to make authoring your first Istio contribution easier than ever with improved integration with GitHub Codespaces, and regular triage of good first issues! If you’re interested in contributing, we can always use help on Issues labeled User Experience and Documentation. If you’d like to get more involved, consider joining our release manager rotation, which will provide you with two releases as a shadow before taking on primary release management responsibilities. We will also aim to provide better recognition to our contributors through a revamped workgroup leads program, where top contributors can be recognized for their expertise! With these initiatives, we believe we are setting up the Istio community to grow for years to come. | ||
|
||
## Conclusion | ||
|
||
This roadmap outlines an exciting near-term for Istio, focusing on a seamless migration path from sidecar to ambient mode, enhanced multi-cluster capabilities, and a refined approach to extensibility. We are also committed to fostering a more welcoming and rewarding environment for our invaluable contributors. These initiatives solidify Istio's position as the leading service mesh, ready to empower cloud native developers with unmatched efficiency, control, and a thriving community. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I'm sure linkerd would have something to say about "fastest". Should we reword to "most robust" or "most trusted"?