Dubbo3.0如何对接istio+envoy的service mesh模式
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
- [x] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
## Ask your question here
请问Dubbo3.0如何对接istio+envoy的service mesh模式。是关闭掉注册中心改为服务直连么?那么其中元数据中是否还需要?
How does Dubbo3.0 connect to istio+envoy service mesh mode? Close the registry and switch to direct service? Is it still needed in the metadata?
```JAVA
@DubboReference(url = "tri://myServiceName")
RpcService rpcService;
```
Contributor guide
Research direction
Start with the @DubboReference(url = "tri://myServiceName") entry point and review how Dubbo 3.0 handles service-mesh integration. Determine whether the registry and metadata are still required when using Istio and Envoy, then document a clear supported configuration and usage answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100