You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we've been talking with different potential users. During the communication, I often found that we do not have features (or demos) they want to use, and they don't want to use the features we set as goals for the year.
I believe that a good roadmap should be based on users' voice instead of just YY by maintainers :)
So I put the information and problems to solve here for discussion.
Hope these problems can help us decide a good roadmap.
They want to deploy their apps on multiple clouds while keeping things simple. Simplicity is really important and I believe they won't like service mesh
Y
VM, and their own docker scheduler
NO
Service registry
?
?
NO
NO
?
They are doing research on sidecar because they have the pain of pushing the business side to upgrade their sdk. They use dubbo techstack for RPC. Introducing Service mesh is almost impossible for them because it's hard to persuade all the business department
Bottlenecks
Based on info above, I suppose that the current bottlenecks are not data plane, but:
Deployment and operation
Integration with different Control planes (I didn't see anyone using Istio)
Coexist with the existing service registry& discovery system and be lightweight. Asking users to "replace your K8s service or dubbo with my Service mesh" is not practical.
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue or help wanted. Thank you for your contributions.
Recently we've been talking with different potential users. During the communication, I often found that we do not have features (or demos) they want to use, and they don't want to use the features we set as goals for the year.
I believe that a good roadmap should be based on users' voice instead of just YY by maintainers :)
So I put the information and problems to solve here for discussion.
Hope these problems can help us decide a good roadmap.
Collection of user requirements
I highlight the "unsupported features or demos"
Bottlenecks
Based on info above, I suppose that the current bottlenecks are not data plane, but:
Roadmap?
I propose that the P1 features are:
The text was updated successfully, but these errors were encountered: