diff --git a/content/zh-cn/overview/tasks/mesh/_index.md b/content/zh-cn/overview/tasks/mesh/_index.md index 7305f8e6cdfd..07b3d1a1819b 100755 --- a/content/zh-cn/overview/tasks/mesh/_index.md +++ b/content/zh-cn/overview/tasks/mesh/_index.md @@ -1,13 +1,12 @@ --- aliases: - /zh/overview/tasks/mesh/ -description: '演示多种部署形态的 Dubbo Mesh 解决方案，以及 Dubbo Mesh 如何帮助用户实现架构的平滑迁移。 ' +description: 演示多种部署形态的 Dubbo Mesh 解决方案，以及 Dubbo Mesh 如何帮助用户实现架构的平滑迁移。 linkTitle: 服务网格 no_list: true title: 服务网格 -toc_hide: true type: docs -weight: 70 +weight: 10 --- @@ -20,7 +19,7 @@ weight: 70

- Istio & Envoy Bookinfo 示例 + Istio & Envoy 示例

演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系。

@@ -30,22 +29,12 @@ weight: 70

- Istio & Proxyless Bookinfo 示例 + Istio & Proxyless 示例

演示 Dubbo Proxyless 接入 Istio 服务网格体系。

-
-
-
-

- 老集群平滑迁移 -

-

演示传统 Dubbo 微服务集群如何平滑迁移到 Istio 服务网格

-
-
-
diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/_index.md deleted file mode 100755 index 54d47ae99940..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/_index.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-proxyless/ -description: 通过完整的 Bookinfo 示例操作演示 Dubbo Proxyless 接入 Istio 服务网格体系。 -linkTitle: Proxyless Bookinfo -no_list: true -title: Proxyless Bookinfo 示例 -type: docs -weight: 70 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Traffic Management -

-

Tasks that demonstrates how to use Istio's traffic routing features.

-
-
-
-
-
-
-

- Security -

-

Demonstrates how to secure Dubbo proxyless mesh.

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/_index.md deleted file mode 100755 index b029e904daea..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/_index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-proxyless/security/ -description: Envoy Security Bookinfo 示例。 -linkTitle: security -no_list: true -title: Envoy Bookinfo 认证鉴权示例 -type: docs -weight: 20 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系，如何配置认证鉴权体系。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Request Routing -

-

This task shows you how to configure dynamic request routing to multiple versions of a microservice.

-
-
-
-
-
-
-

- Traffic Shifting -

-

Shows you how to migrate traffic from an old to new version of a service.

-
-
-
-
-
-
-

- TCP Traffic Shifting -

Shows you how to migrate TCP traffic from an old to new version of a TCP service.

-

-

-
-
-
-
-
-
-

- Request Timeouts -

This task shows you how to set up request timeouts in Envoy using Istio.

-

-

-
-
-
-
-
-
-

- Mirroring -

This task demonstrates the traffic mirroring/shadowing capabilities of Istio.

-

-

-
-
-
-
-
-
-

- Locality Load Balancing -

This series of tasks demonstrate how to configure locality load balancing in Istio.

-

-

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/request-routing.md b/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/request-routing.md deleted file mode 100644 index 559ec400a448..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/security/request-routing.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-proxyless/security/request-routing/ -description: This task shows you how to route requests dynamically to multiple versions of a microservice. -linkTitle: Request Routing -title: Request Routing -toc_hide: true -type: docs -weight: 1 ---- - - - -Before you begin -Setup Istio by following the instructions in the Installation guide. - -Deploy the Bookinfo sample application. - -Review the Traffic Management concepts doc. - -About this task -The Istio Bookinfo sample consists of four separate microservices, each with multiple versions. Three different versions of one of the microservices, reviews, have been deployed and are running concurrently. To illustrate the problem this causes, access the Bookinfo app’s /productpage in a browser and refresh several times. The URL is http://$GATEWAY_URL/productpage, where $GATEWAY_URL is the External IP address of the ingress, as explained in the Bookinfo doc. - -You’ll notice that sometimes the book review output contains star ratings and other times it does not. This is because without an explicit default service version to route to, Istio routes requests to all available versions in a round robin fashion. - -The initial goal of this task is to apply rules that route all traffic to v1 (version 1) of the microservices. Later, you will apply a rule to route traffic based on the value of an HTTP request header. - -Route to version 1 -To route to one version only, you configure route rules that send traffic to default versions for the microservices. - -If you haven’t already, follow the instructions in define the service versions. -Run the following command to create the route rules: -Istio classicGateway API -Istio uses virtual services to define route rules. Run the following command to apply virtual services that will route all traffic to v1 of each microservice: - -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -Because configuration propagation is eventually consistent, wait a few seconds for the virtual services to take effect. - -Display the defined routes with the following command: -Istio classicGateway API -$ kubectl get virtualservices -o yaml -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - details - http: - - route: - - destination: - host: details - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - productpage - http: - - route: - - destination: - host: productpage - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - ratings - http: - - route: - - destination: - host: ratings - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - reviews - http: - - route: - - destination: - host: reviews - subset: v1 -You can also display the corresponding subset definitions with the following command: - -$ kubectl get destinationrules -o yaml -You have configured Istio to route to the v1 version of the Bookinfo microservices, most importantly the reviews service version 1. - -Test the new routing configuration -You can easily test the new configuration by once again refreshing the /productpage of the Bookinfo app in your browser. Notice that the reviews part of the page displays with no rating stars, no matter how many times you refresh. This is because you configured Istio to route all traffic for the reviews service to the version reviews:v1 and this version of the service does not access the star ratings service. - -You have successfully accomplished the first part of this task: route traffic to one version of a service. - -Route based on user identity -Next, you will change the route configuration so that all traffic from a specific user is routed to a specific service version. In this case, all traffic from a user named Jason will be routed to the service reviews:v2. - -This example is enabled by the fact that the productpage service adds a custom end-user header to all outbound HTTP requests to the reviews service. - -Istio also supports routing based on strongly authenticated JWT on ingress gateway, refer to the JWT claim based routing for more details. - -Remember, reviews:v2 is the version that includes the star ratings feature. - -Run the following command to enable user-based routing: -Istio classicGateway API -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml@ -You can confirm the rule is created using the following command: - -$ kubectl get virtualservice reviews -o yaml -apiVersion: networking.istio.io/v1beta1 -kind: VirtualService -... -spec: - hosts: - - reviews - http: - - match: - - headers: - end-user: - exact: jason - route: - - destination: - host: reviews - subset: v2 - - route: - - destination: - host: reviews - subset: v1 -On the /productpage of the Bookinfo app, log in as user jason. - -Refresh the browser. What do you see? The star ratings appear next to each review. - -Log in as another user (pick any name you wish). - -Refresh the browser. Now the stars are gone. This is because traffic is routed to reviews:v1 for all users except Jason. - -You have successfully configured Istio to route traffic based on user identity. - -Understanding what happened -In this task, you used Istio to send 100% of the traffic to the v1 version of each of the Bookinfo services. You then set a rule to selectively send traffic to version v2 of the reviews service based on a custom end-user header added to the request by the productpage service. - -Note that Kubernetes services, like the Bookinfo ones used in this task, must adhere to certain restrictions to take advantage of Istio’s L7 routing features. Refer to the Requirements for Pods and Services for details. - -In the traffic shifting task, you will follow the same basic pattern you learned here to configure route rules to gradually send traffic from one version of a service to another. - -Cleanup -Remove the application route rules: -Istio classicGateway API -$ kubectl delete -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -If you are not planning to explore any follow-on tasks, refer to the Bookinfo cleanup instructions to shutdown the application. \ No newline at end of file diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/_index.md deleted file mode 100755 index 81a00fb252c5..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/_index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-proxyless/traffic/ -description: Envoy Traffic Management Bookinfo 示例。 -linkTitle: Traffic Management -no_list: true -title: Envoy Bookinfo 流量管控示例 -type: docs -weight: 10 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系，如何进行流量管理。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Request Routing -

-

This task shows you how to configure dynamic request routing to multiple versions of a microservice.

-
-
-
-
-
-
-

- Traffic Shifting -

-

Shows you how to migrate traffic from an old to new version of a service.

-
-
-
-
-
-
-

- TCP Traffic Shifting -

Shows you how to migrate TCP traffic from an old to new version of a TCP service.

-

-

-
-
-
-
-
-
-

- Request Timeouts -

This task shows you how to set up request timeouts in Envoy using Istio.

-

-

-
-
-
-
-
-
-

- Mirroring -

This task demonstrates the traffic mirroring/shadowing capabilities of Istio.

-

-

-
-
-
-
-
-
-

- Locality Load Balancing -

This series of tasks demonstrate how to configure locality load balancing in Istio.

-

-

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/request-routing.md b/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/request-routing.md deleted file mode 100644 index 9e277a3a658a..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-proxyless/traffic/request-routing.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-proxyless/traffic/request-routing/ -description: This task shows you how to route requests dynamically to multiple versions of a microservice. -linkTitle: Request Routing -title: Request Routing -toc_hide: true -type: docs -weight: 1 ---- - - - -Before you begin -Setup Istio by following the instructions in the Installation guide. - -Deploy the Bookinfo sample application. - -Review the Traffic Management concepts doc. - -About this task -The Istio Bookinfo sample consists of four separate microservices, each with multiple versions. Three different versions of one of the microservices, reviews, have been deployed and are running concurrently. To illustrate the problem this causes, access the Bookinfo app’s /productpage in a browser and refresh several times. The URL is http://$GATEWAY_URL/productpage, where $GATEWAY_URL is the External IP address of the ingress, as explained in the Bookinfo doc. - -You’ll notice that sometimes the book review output contains star ratings and other times it does not. This is because without an explicit default service version to route to, Istio routes requests to all available versions in a round robin fashion. - -The initial goal of this task is to apply rules that route all traffic to v1 (version 1) of the microservices. Later, you will apply a rule to route traffic based on the value of an HTTP request header. - -Route to version 1 -To route to one version only, you configure route rules that send traffic to default versions for the microservices. - -If you haven’t already, follow the instructions in define the service versions. -Run the following command to create the route rules: -Istio classicGateway API -Istio uses virtual services to define route rules. Run the following command to apply virtual services that will route all traffic to v1 of each microservice: - -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -Because configuration propagation is eventually consistent, wait a few seconds for the virtual services to take effect. - -Display the defined routes with the following command: -Istio classicGateway API -$ kubectl get virtualservices -o yaml -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - details - http: - - route: - - destination: - host: details - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - productpage - http: - - route: - - destination: - host: productpage - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - ratings - http: - - route: - - destination: - host: ratings - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - reviews - http: - - route: - - destination: - host: reviews - subset: v1 -You can also display the corresponding subset definitions with the following command: - -$ kubectl get destinationrules -o yaml -You have configured Istio to route to the v1 version of the Bookinfo microservices, most importantly the reviews service version 1. - -Test the new routing configuration -You can easily test the new configuration by once again refreshing the /productpage of the Bookinfo app in your browser. Notice that the reviews part of the page displays with no rating stars, no matter how many times you refresh. This is because you configured Istio to route all traffic for the reviews service to the version reviews:v1 and this version of the service does not access the star ratings service. - -You have successfully accomplished the first part of this task: route traffic to one version of a service. - -Route based on user identity -Next, you will change the route configuration so that all traffic from a specific user is routed to a specific service version. In this case, all traffic from a user named Jason will be routed to the service reviews:v2. - -This example is enabled by the fact that the productpage service adds a custom end-user header to all outbound HTTP requests to the reviews service. - -Istio also supports routing based on strongly authenticated JWT on ingress gateway, refer to the JWT claim based routing for more details. - -Remember, reviews:v2 is the version that includes the star ratings feature. - -Run the following command to enable user-based routing: -Istio classicGateway API -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml@ -You can confirm the rule is created using the following command: - -$ kubectl get virtualservice reviews -o yaml -apiVersion: networking.istio.io/v1beta1 -kind: VirtualService -... -spec: - hosts: - - reviews - http: - - match: - - headers: - end-user: - exact: jason - route: - - destination: - host: reviews - subset: v2 - - route: - - destination: - host: reviews - subset: v1 -On the /productpage of the Bookinfo app, log in as user jason. - -Refresh the browser. What do you see? The star ratings appear next to each review. - -Log in as another user (pick any name you wish). - -Refresh the browser. Now the stars are gone. This is because traffic is routed to reviews:v1 for all users except Jason. - -You have successfully configured Istio to route traffic based on user identity. - -Understanding what happened -In this task, you used Istio to send 100% of the traffic to the v1 version of each of the Bookinfo services. You then set a rule to selectively send traffic to version v2 of the reviews service based on a custom end-user header added to the request by the productpage service. - -Note that Kubernetes services, like the Bookinfo ones used in this task, must adhere to certain restrictions to take advantage of Istio’s L7 routing features. Refer to the Requirements for Pods and Services for details. - -In the traffic shifting task, you will follow the same basic pattern you learned here to configure route rules to gradually send traffic from one version of a service to another. - -Cleanup -Remove the application route rules: -Istio classicGateway API -$ kubectl delete -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -If you are not planning to explore any follow-on tasks, refer to the Bookinfo cleanup instructions to shutdown the application. \ No newline at end of file diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/_index.md deleted file mode 100755 index b046e564d62f..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/_index.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-sidecar/ -description: 通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系。 -linkTitle: Envoy Bookinfo -no_list: true -title: Envoy Bookinfo 示例 -type: docs -weight: 70 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Traffic Management -

-

Tasks that demonstrates how to use Istio's traffic routing features.

-
-
-
-
-
-
-

- Security -

-

Demonstrates how to secure Dubbo mesh.

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/_index.md deleted file mode 100755 index c803952b16fc..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/_index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-sidecar/security/ -description: Envoy Security Bookinfo 示例。 -linkTitle: security -no_list: true -title: Envoy Bookinfo 认证鉴权示例 -type: docs -weight: 20 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系，如何配置认证鉴权体系。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Request Routing -

-

This task shows you how to configure dynamic request routing to multiple versions of a microservice.

-
-
-
-
-
-
-

- Traffic Shifting -

-

Shows you how to migrate traffic from an old to new version of a service.

-
-
-
-
-
-
-

- TCP Traffic Shifting -

Shows you how to migrate TCP traffic from an old to new version of a TCP service.

-

-

-
-
-
-
-
-
-

- Request Timeouts -

This task shows you how to set up request timeouts in Envoy using Istio.

-

-

-
-
-
-
-
-
-

- Mirroring -

This task demonstrates the traffic mirroring/shadowing capabilities of Istio.

-

-

-
-
-
-
-
-
-

- Locality Load Balancing -

This series of tasks demonstrate how to configure locality load balancing in Istio.

-

-

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/request-routing.md b/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/request-routing.md deleted file mode 100644 index 18ca76bb0ce1..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/security/request-routing.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-sidecar/security/request-routing/ -description: This task shows you how to route requests dynamically to multiple versions of a microservice. -linkTitle: Request Routing -title: Request Routing -toc_hide: true -type: docs -weight: 1 ---- - - - -Before you begin -Setup Istio by following the instructions in the Installation guide. - -Deploy the Bookinfo sample application. - -Review the Traffic Management concepts doc. - -About this task -The Istio Bookinfo sample consists of four separate microservices, each with multiple versions. Three different versions of one of the microservices, reviews, have been deployed and are running concurrently. To illustrate the problem this causes, access the Bookinfo app’s /productpage in a browser and refresh several times. The URL is http://$GATEWAY_URL/productpage, where $GATEWAY_URL is the External IP address of the ingress, as explained in the Bookinfo doc. - -You’ll notice that sometimes the book review output contains star ratings and other times it does not. This is because without an explicit default service version to route to, Istio routes requests to all available versions in a round robin fashion. - -The initial goal of this task is to apply rules that route all traffic to v1 (version 1) of the microservices. Later, you will apply a rule to route traffic based on the value of an HTTP request header. - -Route to version 1 -To route to one version only, you configure route rules that send traffic to default versions for the microservices. - -If you haven’t already, follow the instructions in define the service versions. -Run the following command to create the route rules: -Istio classicGateway API -Istio uses virtual services to define route rules. Run the following command to apply virtual services that will route all traffic to v1 of each microservice: - -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -Because configuration propagation is eventually consistent, wait a few seconds for the virtual services to take effect. - -Display the defined routes with the following command: -Istio classicGateway API -$ kubectl get virtualservices -o yaml -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - details - http: - - route: - - destination: - host: details - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - productpage - http: - - route: - - destination: - host: productpage - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - ratings - http: - - route: - - destination: - host: ratings - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - reviews - http: - - route: - - destination: - host: reviews - subset: v1 -You can also display the corresponding subset definitions with the following command: - -$ kubectl get destinationrules -o yaml -You have configured Istio to route to the v1 version of the Bookinfo microservices, most importantly the reviews service version 1. - -Test the new routing configuration -You can easily test the new configuration by once again refreshing the /productpage of the Bookinfo app in your browser. Notice that the reviews part of the page displays with no rating stars, no matter how many times you refresh. This is because you configured Istio to route all traffic for the reviews service to the version reviews:v1 and this version of the service does not access the star ratings service. - -You have successfully accomplished the first part of this task: route traffic to one version of a service. - -Route based on user identity -Next, you will change the route configuration so that all traffic from a specific user is routed to a specific service version. In this case, all traffic from a user named Jason will be routed to the service reviews:v2. - -This example is enabled by the fact that the productpage service adds a custom end-user header to all outbound HTTP requests to the reviews service. - -Istio also supports routing based on strongly authenticated JWT on ingress gateway, refer to the JWT claim based routing for more details. - -Remember, reviews:v2 is the version that includes the star ratings feature. - -Run the following command to enable user-based routing: -Istio classicGateway API -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml@ -You can confirm the rule is created using the following command: - -$ kubectl get virtualservice reviews -o yaml -apiVersion: networking.istio.io/v1beta1 -kind: VirtualService -... -spec: - hosts: - - reviews - http: - - match: - - headers: - end-user: - exact: jason - route: - - destination: - host: reviews - subset: v2 - - route: - - destination: - host: reviews - subset: v1 -On the /productpage of the Bookinfo app, log in as user jason. - -Refresh the browser. What do you see? The star ratings appear next to each review. - -Log in as another user (pick any name you wish). - -Refresh the browser. Now the stars are gone. This is because traffic is routed to reviews:v1 for all users except Jason. - -You have successfully configured Istio to route traffic based on user identity. - -Understanding what happened -In this task, you used Istio to send 100% of the traffic to the v1 version of each of the Bookinfo services. You then set a rule to selectively send traffic to version v2 of the reviews service based on a custom end-user header added to the request by the productpage service. - -Note that Kubernetes services, like the Bookinfo ones used in this task, must adhere to certain restrictions to take advantage of Istio’s L7 routing features. Refer to the Requirements for Pods and Services for details. - -In the traffic shifting task, you will follow the same basic pattern you learned here to configure route rules to gradually send traffic from one version of a service to another. - -Cleanup -Remove the application route rules: -Istio classicGateway API -$ kubectl delete -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -If you are not planning to explore any follow-on tasks, refer to the Bookinfo cleanup instructions to shutdown the application. \ No newline at end of file diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/_index.md b/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/_index.md deleted file mode 100755 index 10741f9f5a38..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/_index.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-sidecar/traffic/ -description: Envoy Traffic Management Bookinfo 示例。 -linkTitle: Traffic Management -no_list: true -title: Envoy Bookinfo 流量管控示例 -type: docs -weight: 10 ---- - - - -通过完整的 Bookinfo 示例操作演示 Dubbo 服务接入基于 Envoy 代理的 Istio 服务网格体系，如何进行流量管理。 - -{{< blocks/section color="white" height="auto">}} -{{< /blocks/section >}} - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- Request Routing -

-

This task shows you how to configure dynamic request routing to multiple versions of a microservice.

-
-
-
-
-
-
-

- Traffic Shifting -

-

Shows you how to migrate traffic from an old to new version of a service.

-
-
-
-
-
-
-

- TCP Traffic Shifting -

Shows you how to migrate TCP traffic from an old to new version of a TCP service.

-

-

-
-
-
-
-
-
-

- Request Timeouts -

This task shows you how to set up request timeouts in Envoy using Istio.

-

-

-
-
-
-
-
-
-

- Mirroring -

This task demonstrates the traffic mirroring/shadowing capabilities of Istio.

-

-

-
-
-
-
-
-
-

- Locality Load Balancing -

This series of tasks demonstrate how to configure locality load balancing in Istio.

-

-

-
-
-
-
-
-
- -{{< /blocks/section >}} diff --git a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/request-routing.md b/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/request-routing.md deleted file mode 100644 index 43718d07468c..000000000000 --- a/content/zh-cn/overview/tasks/mesh/bookinfo-sidecar/traffic/request-routing.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/bookinfo-sidecar/traffic/request-routing/ -description: This task shows you how to route requests dynamically to multiple versions of a microservice. -linkTitle: Request Routing -title: Request Routing -toc_hide: true -type: docs -weight: 1 ---- - - - -Before you begin -Setup Istio by following the instructions in the Installation guide. - -Deploy the Bookinfo sample application. - -Review the Traffic Management concepts doc. - -About this task -The Istio Bookinfo sample consists of four separate microservices, each with multiple versions. Three different versions of one of the microservices, reviews, have been deployed and are running concurrently. To illustrate the problem this causes, access the Bookinfo app’s /productpage in a browser and refresh several times. The URL is http://$GATEWAY_URL/productpage, where $GATEWAY_URL is the External IP address of the ingress, as explained in the Bookinfo doc. - -You’ll notice that sometimes the book review output contains star ratings and other times it does not. This is because without an explicit default service version to route to, Istio routes requests to all available versions in a round robin fashion. - -The initial goal of this task is to apply rules that route all traffic to v1 (version 1) of the microservices. Later, you will apply a rule to route traffic based on the value of an HTTP request header. - -Route to version 1 -To route to one version only, you configure route rules that send traffic to default versions for the microservices. - -If you haven’t already, follow the instructions in define the service versions. -Run the following command to create the route rules: -Istio classicGateway API -Istio uses virtual services to define route rules. Run the following command to apply virtual services that will route all traffic to v1 of each microservice: - -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -Because configuration propagation is eventually consistent, wait a few seconds for the virtual services to take effect. - -Display the defined routes with the following command: -Istio classicGateway API -$ kubectl get virtualservices -o yaml -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - details - http: - - route: - - destination: - host: details - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - productpage - http: - - route: - - destination: - host: productpage - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - ratings - http: - - route: - - destination: - host: ratings - subset: v1 -- apiVersion: networking.istio.io/v1beta1 - kind: VirtualService - ... - spec: - hosts: - - reviews - http: - - route: - - destination: - host: reviews - subset: v1 -You can also display the corresponding subset definitions with the following command: - -$ kubectl get destinationrules -o yaml -You have configured Istio to route to the v1 version of the Bookinfo microservices, most importantly the reviews service version 1. - -Test the new routing configuration -You can easily test the new configuration by once again refreshing the /productpage of the Bookinfo app in your browser. Notice that the reviews part of the page displays with no rating stars, no matter how many times you refresh. This is because you configured Istio to route all traffic for the reviews service to the version reviews:v1 and this version of the service does not access the star ratings service. - -You have successfully accomplished the first part of this task: route traffic to one version of a service. - -Route based on user identity -Next, you will change the route configuration so that all traffic from a specific user is routed to a specific service version. In this case, all traffic from a user named Jason will be routed to the service reviews:v2. - -This example is enabled by the fact that the productpage service adds a custom end-user header to all outbound HTTP requests to the reviews service. - -Istio also supports routing based on strongly authenticated JWT on ingress gateway, refer to the JWT claim based routing for more details. - -Remember, reviews:v2 is the version that includes the star ratings feature. - -Run the following command to enable user-based routing: -Istio classicGateway API -$ kubectl apply -f @samples/bookinfo/networking/virtual-service-reviews-test-v2.yaml@ -You can confirm the rule is created using the following command: - -$ kubectl get virtualservice reviews -o yaml -apiVersion: networking.istio.io/v1beta1 -kind: VirtualService -... -spec: - hosts: - - reviews - http: - - match: - - headers: - end-user: - exact: jason - route: - - destination: - host: reviews - subset: v2 - - route: - - destination: - host: reviews - subset: v1 -On the /productpage of the Bookinfo app, log in as user jason. - -Refresh the browser. What do you see? The star ratings appear next to each review. - -Log in as another user (pick any name you wish). - -Refresh the browser. Now the stars are gone. This is because traffic is routed to reviews:v1 for all users except Jason. - -You have successfully configured Istio to route traffic based on user identity. - -Understanding what happened -In this task, you used Istio to send 100% of the traffic to the v1 version of each of the Bookinfo services. You then set a rule to selectively send traffic to version v2 of the reviews service based on a custom end-user header added to the request by the productpage service. - -Note that Kubernetes services, like the Bookinfo ones used in this task, must adhere to certain restrictions to take advantage of Istio’s L7 routing features. Refer to the Requirements for Pods and Services for details. - -In the traffic shifting task, you will follow the same basic pattern you learned here to configure route rules to gradually send traffic from one version of a service to another. - -Cleanup -Remove the application route rules: -Istio classicGateway API -$ kubectl delete -f @samples/bookinfo/networking/virtual-service-all-v1.yaml@ -If you are not planning to explore any follow-on tasks, refer to the Bookinfo cleanup instructions to shutdown the application. \ No newline at end of file diff --git a/content/zh-cn/overview/tasks/mesh/migration/dubbo-mesh.md b/content/zh-cn/overview/tasks/mesh/dubbo-mesh.md similarity index 97% rename from content/zh-cn/overview/tasks/mesh/migration/dubbo-mesh.md rename to content/zh-cn/overview/tasks/mesh/dubbo-mesh.md index 59f70ba2d555..22b39fa92c7e 100644 --- a/content/zh-cn/overview/tasks/mesh/migration/dubbo-mesh.md +++ b/content/zh-cn/overview/tasks/mesh/dubbo-mesh.md @@ -1,9 +1,9 @@ --- aliases: - /zh/overview/tasks/mesh/migration/dubbo-mesh/ -description: 本示例演示了如何使用 Istio+Envoy 的 Service Mesh 部署模式开发 Dubbo3 服务。Dubbo3 服务使用 Triple 作为通信协议，通信过程经过 Envoy 数据面拦截，同时使用标准 Istio 的流量治理能力治理 Dubbo。 -linkTitle: 地址同步 -title: 地址同步 +description: 演示了 Dubbo3 的 Sidecar Mesh 模式。 +linkTitle: Sidecar 模式 +title: Sidecar 模式 type: docs weight: 1 --- diff --git a/content/zh-cn/overview/tasks/mesh/migration/_index.md b/content/zh-cn/overview/tasks/mesh/migration/_index.md deleted file mode 100755 index 431646548ca4..000000000000 --- a/content/zh-cn/overview/tasks/mesh/migration/_index.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -aliases: - - /zh/overview/tasks/mesh/migration/ -description: 演示 Dubbo Mesh 如何帮助用户实现架构的平滑迁移。 -linkTitle: Dubbo2 平滑迁移 -no_list: true -title: 传统 Dubbo 微服务集群如何平滑迁移到 Istio 服务网格体系 -type: docs -weight: 70 ---- - - - -{{< blocks/section color="white" height="auto">}} -
-
-
-
-
-
-

- 地址同步问题 -

-

如何解决地址同步问题？

-
-
-
-
-
-
-

- 协议识别问题 -

-

如何解决 Dubbo2+hessian2 协议问题？

-
-
-
-
-
-
- -{{< /blocks/section >}} \ No newline at end of file diff --git a/content/zh-cn/overview/tasks/mesh/migration/deploy-on-k8s.md b/content/zh-cn/overview/tasks/mesh/migration/deploy-on-k8s.md index aa88e33a51a4..7da2e7e5b8f9 100644 --- a/content/zh-cn/overview/tasks/mesh/migration/deploy-on-k8s.md +++ b/content/zh-cn/overview/tasks/mesh/migration/deploy-on-k8s.md @@ -2,10 +2,11 @@ aliases: - /zh/overview/tasks/mesh/migration/deploy-on-k8s/ description: 该示例演示了直接以 API-SERVER 为注册中心，将 Dubbo 应用部署到 Kubernetes 并复用 Kubernetes Native Service 的使用示例。 此示例的局限在于需要授予每个 Dubbo 应用访问 API-SERVER 特定资源的权限，同时直接访问和监听 API-SERVER 对中小集群来说并没有什么问题， 但对于较大规模集群而言可能给 API-SERVER 的稳定性带来一定的考验。除此之外，可以考虑配合 Dubbo 控制面将 Dubbo 应用部署到 Kuberntes 的方案， 该方案无需授予 Dubbo 应用访问 API-SERVER 的权限，也无需为 API-SERVER 引连接过多数据面造成的稳定性而担心。 -linkTitle: 协议识别 -title: 协议识别 +linkTitle: 部署到 Kubernetes 集群 +title: 部署到 Kubernetes 集群 type: docs -weight: 2 +toc_hide: true +weight: 70 --- diff --git a/content/zh-cn/overview/tasks/mesh/migration/proxyless.md b/content/zh-cn/overview/tasks/mesh/proxyless.md similarity index 98% rename from content/zh-cn/overview/tasks/mesh/migration/proxyless.md rename to content/zh-cn/overview/tasks/mesh/proxyless.md index 657a2dab8892..ca330702f5e3 100644 --- a/content/zh-cn/overview/tasks/mesh/migration/proxyless.md +++ b/content/zh-cn/overview/tasks/mesh/proxyless.md @@ -1,9 +1,9 @@ --- aliases: - /zh/overview/tasks/mesh/migration/proxyless/ -description: "" -linkTitle: 其他问题？ -title: 其他问题？ +description: 演示了 Dubbo3 的 Proxyless 模式。 +linkTitle: Proxyless 模式 +title: Proxyless 模式 type: docs weight: 3 ---