From eb9c4069fd90ed760a779c3bf014a547c1d9c8c7 Mon Sep 17 00:00:00 2001 From: devleejb Date: Tue, 28 May 2024 23:26:59 +0900 Subject: [PATCH 1/2] Change istio `profile=external` to `profile=remote` Signed-off-by: devleejb --- .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ .../working-with-istio-on-non-flat-network.md | 16 ++++++++++------ 16 files changed, 160 insertions(+), 96 deletions(-) diff --git a/docs/userguide/service/working-with-istio-on-non-flat-network.md b/docs/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/docs/userguide/service/working-with-istio-on-non-flat-network.md +++ b/docs/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/current/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md index a9a1dd3c..d69783ee 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md index a9a1dd3c..d69783ee 100644 --- a/versioned_docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.3/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.4/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.5/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.6/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.7/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.8/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) diff --git a/versioned_docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md b/versioned_docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md index e9ceab55..df33592e 100644 --- a/versioned_docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md +++ b/versioned_docs/version-v1.9/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,12 +11,14 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) -*** +--- + The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It cannot implement the function of service topology for application deployed by `karmada`. I will continue to provide a new solution later that deploys `istiod` on the `karmada-host`. -*** + +--- ## Install Karmada @@ -27,9 +29,11 @@ in Quick Start, you can get a Karmada. ## Deploy Istio -*** +--- + If you are testing multicluster setup on `kind` you can use [MetalLB](https://metallb.universe.tf/installation/) to make use of `EXTERNAL-IP` for `LoadBalancer` services. -*** + +--- ### Install istioctl @@ -155,7 +159,7 @@ EOF Run the following command to install istio CRDs on karmada apiserver: ```bash -istioctl manifest generate --set profile=external \ +istioctl manifest generate --set profile=remote \ --set values.global.configCluster=true \ --set values.global.externalIstiod=false \ --set values.global.defaultPodDisruptionBudget.enabled=false \ @@ -269,4 +273,4 @@ samples/multicluster/gen-eastwest-gateway.sh --mesh mesh1 --cluster member2 --ne ### Deploy bookinfo application -See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) \ No newline at end of file +See module `Deploy bookinfo application` in [here](./working-with-istio-on-flat-network.md#deploy-bookinfo-application) From 810ba7bbb160705db08f91b96d6eddad8c5e3cc0 Mon Sep 17 00:00:00 2001 From: LeeJongBeom <52884648+devleejb@users.noreply.github.com> Date: Thu, 11 Jul 2024 22:29:47 +0900 Subject: [PATCH 2/2] Update docs/userguide/service/working-with-istio-on-non-flat-network.md Co-authored-by: Michael --- .../userguide/service/working-with-istio-on-non-flat-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide/service/working-with-istio-on-non-flat-network.md b/docs/userguide/service/working-with-istio-on-non-flat-network.md index df33592e..cad58236 100644 --- a/docs/userguide/service/working-with-istio-on-non-flat-network.md +++ b/docs/userguide/service/working-with-istio-on-non-flat-network.md @@ -11,7 +11,7 @@ not direct connectivity between the pods in all clusters. ![Istio on Karmada-different-network](../../resources/userguide/service/istio/istio-on-karmada-different-network.png) ---- +*** The reason for deploying `istiod` on the `member1` is that `kiali` needs to be deployed on the same cluster as `istiod` . If `istiod` and `kiali` are deployed on the `karmada-host`,`kiali` will not find the namespace created by `karmada`. It