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
Copy file name to clipboardExpand all lines: content/en/overview/mesh/concepts/security.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,7 @@ title: Security
5
5
type: docs
6
6
weight: 2
7
7
---
8
-
9
-
Dubbo Service Mesh security provides strong identities, powerful policies, transparent TLS encryption, and authentication tooling to protect your services and data. It follows the same security model as Istio, but is optimized for the Dubbo protocol and sidecarless architecture.
8
+
> The service mesh is currently in an early experimental stage. Standard features will be gradually completed and supported.
10
9
11
10
## High-level architecture
12
11
@@ -130,6 +129,7 @@ After understanding the basic concepts above, you can:
Copy file name to clipboardExpand all lines: content/en/overview/mesh/concepts/traffic-management.md
+28-8Lines changed: 28 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,14 @@ title: Traffic Management
5
5
type: docs
6
6
weight: 1
7
7
---
8
+
> The service mesh is currently in an early experimental stage. Resource naming may change.
8
9
9
-
In Dubbo Service Mesh, traffic management is implemented through the collaboration of the Dubbo control plane and the Dubbo Agent. The control plane generates gRPC xDS configuration based on Kubernetes CRDs and pushes it to Dubbo Agent via the xDS protocol, enabling fine-grained control over inter-service traffic.
10
-
11
-
## Traffic management overview
10
+
## Introduction
12
11
13
12
The traffic management model of Dubbo Service Mesh is aligned with Istio, but optimized for the Dubbo protocol and sidecarless architecture. The core components are:
14
13
15
14
-**ServiceRoute**: defines routing rules and controls how requests are routed to service instances.
16
15
-**SubsetRule**: defines service subsets and traffic policies, such as load balancing, connection pools, TLS settings, etc.
17
-
-**MeshConfig**: mesh-wide configuration, including default traffic policies, trust domain, and more.
18
16
19
17
By configuring these resources, you can achieve traffic routing, load balancing, and resilience without modifying application code.
20
18
@@ -26,7 +24,7 @@ ServiceRoute enables you to:
26
24
- Route traffic to different versions of a service (for example, v1 and v2).
27
25
- Route based on request attributes such as headers and paths.
28
26
- Configure weighted routing for canary and gradual rollouts.
29
-
-(Planned) Configure timeouts and retries for resilience.
27
+
- Configure timeouts and retries for resilience.
30
28
31
29
### ServiceRoute example
32
30
@@ -117,13 +115,35 @@ spec:
117
115
118
116
Subsets are selected based on Pod labels. In the example above, Pods with label `version: v1` are placed into subset `v1`, and Pods with `version: v2` into subset `v2`.
119
117
120
-
## Other notes
118
+
## Gateway
119
+
120
+
Gateways provide unified control over ingress and egress traffic in the mesh, allowing you to specify which traffic is allowed to enter or leave the mesh.
121
+
122
+
Dubbo mesh gateway is implemented based on Kubernetes Gateway API, using Pixiu Gateway as the data plane proxy.
123
+
124
+
### Gateway example
121
125
122
-
Because Dubbo Service Mesh uses a sidecarless architecture, the traditional Sidecar resource is replaced by the Dubbo Agent. The Dubbo Agent is embedded into the application process and communicates with the control plane via the xDS protocol.
126
+
```yaml
127
+
apiVersion: gateway.networking.k8s.io/v1
128
+
kind: Gateway
129
+
metadata:
130
+
name: gateway
131
+
namespace: dubbo-ingress
132
+
spec:
133
+
gatewayClassName: dubbo
134
+
listeners:
135
+
- name: default
136
+
hostname: "*.example.com"
137
+
port: 80
138
+
protocol: HTTP
139
+
allowedRoutes:
140
+
namespaces:
141
+
from: All
142
+
```
123
143
124
144
## Related content
125
145
126
-
- [Dubbo Service Mesh Quickstart](/en/overview/quickstart/)
Copy file name to clipboardExpand all lines: content/en/overview/mesh/getting-started.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,36 +5,36 @@ title: Quickstart
5
5
type: docs
6
6
weight: 1
7
7
---
8
+
> The service mesh is currently in an early experimental stage. Standard features will be gradually completed and supported.
8
9
9
-
Special thanks to [Megan Yahya's KubeCon EU 2021 talk](https://www.youtube.com/watch?v=cGJXkZ7jiDk)for inspiration and related support.
10
+
Dubbo Service Mesh is a proxyless mesh model developed in 2025. This mode introduces no extra proxy forwarding overhead, making it suitable for all performance-sensitive applications and for any deployment environment.
10
11
11
-
Dubbo Service Mesh is a proxyless mesh model developed in 2025. In this model, processes communicate directly and interact with the control plane via the xDS protocol.
12
-
13
-
This mode introduces no extra proxy forwarding overhead, making it suitable for latency-sensitive applications and for any deployment environment.
12
+
- Each deployed application injects a Dubbo Agent that only provides XDS and SDS services, enabling direct inter-service communication through the native gRPC xDS client.
13
+
- All injected agents are based on Kubernetes Gateway API to implement communication between services and external systems.
14
14
15
15
## Download Dubbo
16
16
17
-
1.Go to the Dubbo release page and download the installer for your OS, or automatically download the latest version (Linux or macOS):
17
+
Go to the Dubbo release page and download the installer for your OS, or automatically download the latest version (Linux or macOS):
18
18
19
19
```bash
20
20
curl -L https://dubbo.apache.org/downloadDubbo | sh -
21
21
```
22
22
23
-
2.Change to the Dubbo package directory:
23
+
Change to the Dubbo package directory:
24
24
25
25
```bash
26
26
cd dubbo-x.xx.x
27
27
```
28
28
29
29
## Install Dubbo
30
30
31
-
1.Install Dubbo with the default profile:
31
+
Install Dubbo with the default profile:
32
32
33
33
```bash
34
34
dubboctl install -y
35
35
```
36
36
37
-
2.Label the namespace to tell Dubbo to automatically inject the Dubbo Agent when deploying applications:
37
+
Label the namespace to tell Dubbo to automatically inject the Dubbo Agent when deploying applications:
0 commit comments