multicluster name change

Author: sreejithgs

docs/deploy/multi-cloud-ingress-lb-solution.md

@@ -1,8 +1,8 @@
-# Multi-cloud and multi-cluster ingress and load balancing solution with Amazon EKS and Microsoft AKS clusters
+# Multi-cloud and GSLB solution with Amazon EKS and Microsoft AKS clusters
 
 You can deploy multiple instances of the same application across multiple clouds provided by different cloud providers. This multi-cloud strategy helps you to ensure resiliency, high availability, and proximity. A multi-cloud approach also allows you to take advantage of the best of each cloud provider by reducing the risks such as vendor lock-in and cloud outages.
 
-You can deploy the multi-cloud and multi-cluster ingress and load balancing solution with Amazon EKS and Microsoft AKS.
+You can deploy the multi-cloud and GSLB solution with Amazon EKS and Microsoft AKS.
 
 ## Deployment topology
 
@@ -16,16 +16,16 @@ The following diagram explains a deployment topology of the multi-cloud ingress
   -  You should be familiar with Citrix ADC and [Citrix ADC networking](https://docs.citrix.com/en-us/citrix-adc/current-release/networking.html).
   -  Instances of the same application must be deployed in Kubernetes clusters on Amazon EKS and Microsoft AKS.
 
-## Deploy multi-cloud and multi-cluster ingress and load balancing solution with Amazon EKS and Microsoft AKS clusters
+## Deploy multi-cloud and GSLB solution with Amazon EKS and Microsoft AKS clusters
 
-To deploy the multi-cloud multi-cluster ingress and load balancing solution, you must perform the following tasks.
+To deploy the multi-cloud GSLB solution, you must perform the following tasks.
 
 1.	Deploy Citrix ADC VPX in AWS.
 1.	Deploy Citrix ADC VPX in Azure.
 1.	Configure ADNS service on Citrix ADC VPX deployed in AWS and AKS.
 1.	Configure GSLB service on Citrix ADC VPX deployed in AWS and AKS.
 1.  Apply GTP and GSE CRDs on AWS and Azure Kubernetes clusters.
-1.	Deploy the multi-cluster controller.
+1.	Deploy the GSLB controller.
 
 ## Deploy Citrix ADC VPX in AWS
 
@@ -57,7 +57,7 @@ For high availability (HA), you can install two instances of Citrix ADC VPX in H
 
     **Note**: If you are running the Citrix ADC VPX in High Availability (HA) mode, you must perform this configuration in both of the Citrix ADC VPX instances.
 
-5.  Enable Content Switching (CS), Load Balancing (LB), Global Server Load Balancing(GSLB), and SSL features in Citrix ADC VPX using the following command:
+5.  Enable Content Switching (CS), Load Balancing (LB), Global Server Load Balancing (GSLB), and SSL features in Citrix ADC VPX using the following command:
 
         enable feature *feature*
 
@@ -159,7 +159,7 @@ You must create GSLB sites on Citrix ADC VPX deployed on AWS and Azure.
 
 ## Apply GTP and GSE CRDs on AWS and Azure Kubernetes clusters
 
-The global traffic policy (GTP) and global service entry (GSE) CRDs help to configure Citrix ADC for performing GSLB in Kubernetes applications. These CRDs are designed for configuring multi-cluster ingress and load balancing solution for Kubernetes clusters.
+The global traffic policy (GTP) and global service entry (GSE) CRDs help to configure Citrix ADC for performing GSLB in Kubernetes applications. These CRDs are designed for configuring GSLB solution for Kubernetes clusters.
 
 **GTP CRD**
 
@@ -177,11 +177,11 @@ For the GSE CRD definition, see the [GSE CRD](https://developer-docs.citrix.com/
 
     kubectl apply -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/multicluster/Manifest/gse-crd.yaml
 
-## Deploy multi-cluster controller
+## Deploy GSLB controller
 
-Multi-cluster controller helps you to ensure the high availability of the applications across clusters in a multi-cloud environment.
+GSLB controller helps you to ensure the high availability of the applications across clusters in a multi-cloud environment.
 
-You can install the multi-cluster controller on the AWS and Azure clusters. Multi-cluster controller listens to GTP and GSE CRDs and configures the Citrix ADC for GSLB that provides high availability across multiple regions in a multi-cloud environment.
+You can install the multi-cluster controller on the AWS and Azure clusters. GSLB controller listens to GTP and GSE CRDs and configures the Citrix ADC for GSLB that provides high availability across multiple regions in a multi-cloud environment.
 
 To deploy the multi-cluster controller, perform the following steps:
 
@@ -361,7 +361,7 @@ As the GTP CRD is configured for the traffic policy as `FAILOVER`, Citrix ADC VP
 
 ## Citrix ADC VPX as ingress and GSLB device for Amazon EKS and Microsoft AKS clusters
 
-You can deploy the multi-cloud and multi-cluster ingress and load balancing solution with Amazon EKS and Microsoft AKS with Citrix ADC VPX as GSLB and the same Citrix ADC VPX as ingress device too.
+You can deploy the multi-cloud and GSLB solution with Amazon EKS and Microsoft AKS with Citrix ADC VPX as GSLB and the same Citrix ADC VPX as ingress device too.
 
 To deploy the multi-cloud multi-cluster ingress and load balancing with Citrix ADC VPX as the ingress device, you must complete the following tasks described in the previous sections:
 
@@ -370,7 +370,7 @@ To deploy the multi-cloud multi-cluster ingress and load balancing with Citrix A
 1.	[Configure ADNS service on Citrix ADC VPX deployed in AWS and AKS](#configure-adns-service-on-citrix-adc-vpx-deployed-in-aws-and-aks)
 1.	[Configure GSLB service on Citrix ADC VPX deployed in AWS and AKS](#configure-gslb-service-on-citrix-adc-vpx-deployed-in-aws-and-aks)
 1.  [Apply GTP and GSE CRDs on AWS and Azure Kubernetes clusters](#apply-gtp-and-gse-crds-on-aws-and-azure-kubernetes-clusters)
-1.	[Deploy the multi-cluster controller](#deploy-multi-cluster-controller)
+1.	[Deploy the multi-cluster controller](#deploy-gslb-controller)
 
 After completing the preceding tasks, perform the following tasks:
 

docs/multicluster/multi-cluster.md

@@ -1,22 +1,22 @@
-# Multi-cluster ingress and load balancing solution using the Citrix ingress controller
+# NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters
 
 ## Overview
 
 For ensuring high availability, proximity based load balancing, and scalability, you may need to deploy an application in multiple distributed Kubernetes clusters. When the same application is deployed in multiple Kubernetes clusters, a load balancing decision has to be taken among application instances dispersed across clusters.
 
 For implementing a load balancing solution for distributed Kubernetes clusters, the health of applications across clusters needs to be monitored globally. You need to monitor application availability and performance, update the application status across clusters, collect statistics from endpoints in data centers, and share the statistics across data centers.
 
-Citrix provides a multi-cluster ingress and load balancing solution which globally monitors applications, collect, and share metrics across different clusters, and provides intelligent load balancing decisions. It ensures better performance and reliability for your Kubernetes services that are exposed using Ingress or using type LoadBalancer.
+NetScaler provides a GSLB controller for applications deployed in distributed Kubernetes clusters which globally monitors applications, collect, and share metrics across different clusters, and provides intelligent load balancing decisions. It ensures better performance and reliability for your Kubernetes services that are exposed using Ingress or using type LoadBalancer.
 
 ## Deployment topology
 
-The following diagram explains a deployment topology for the multi-cluster ingress and load balancing solution for Kubernetes clusters.
+The following diagram explains a deployment topology for the NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters for Kubernetes clusters.
 
 **Note:** Services of type LoadBalancer (available for bare metal clusters using Citrix ADC) are also supported.
 
-![Multi-cluster-deployment](../media/multi-cluster-updated.png)
+![gslb-controller-deployment](../media/multi-cluster-updated.png)
 
-This diagram shows a sample topology with two data centers and each data center contains multiple Kubernetes clusters. For data center 1, Citrix ADC CPX is deployed as the Ingress load balancer in each Kubernetes cluster. For data center 2, HAProxy is deployed as the load balancer in each Kubernetes cluster. Citrix multi-cluster ingress and load balancing solution for Kubernetes load balances across the ingresses.
+This diagram shows a sample topology with two data centers and each data center contains multiple Kubernetes clusters. For data center 1, Citrix ADC CPX is deployed as the Ingress load balancer in each Kubernetes cluster. For data center 2, HAProxy is deployed as the load balancer in each Kubernetes cluster. Citrix NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters for Kubernetes load balances across the ingresses.
 
 **Note:** Any ingress solution, including third party solutions such as Istio ingress gateway as well as the Citrix ingress controller with Citrix ADC MPX, VPX, or BLX is supported. This topology is just a sample deployment.
 
@@ -26,7 +26,7 @@ The global server load balancing (GSLB) configuration synchronization option of
 
 Each cluster in the deployment runs an instance of the GSLB Kubernetes controller. GSLB controller is the module responsible for the configuration of the Citrix ADC GSLB device. The GSLB controller configures the GSLB master device for the applications deployed in their respective cluster. The GSLB master device pushes the GSLB configuration to the remaining GSLB subordinate devices using the GSLB sync feature. When you synchronize a GSLB configuration, the configurations on all the GSLB sites participating in the GSLB setup are made similar to the configuration on the master site.
 
-The multi-cluster ingress and load balancing solution can be applied for any Kubernetes object which is used to route traffic into the cluster.
+The NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters can be applied for any Kubernetes object which is used to route traffic into the cluster.
 
 The following global load balancing methods are supported:
 
@@ -51,7 +51,7 @@ The following deployment types are supported:
 **Note:**
   Currently, IPv6 is not supported.
 
-## CRDs for configuring Multi-cluster ingress and load balancing solution for Kubernetes clusters
+## CRDs for configuring NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters
 
 The following CRDs are introduced to support the Citrix ADC configuration for performing GSLB of Kubernetes applications.
 
@@ -68,14 +68,14 @@ The GTP CRD spec is available in the Citrix ingress controller GitHub repo at: [
 
 GSE CRD dictates the endpoint information (any Kubernetes object which routes traffic into the cluster) in each cluster.
 
-The GSE CRD Spec is available in the citrix ingress controller GitHub repo at: [gse-crd.yaml](https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/multicluster/Manifest/gse-crd.yaml)
+The GSE CRD Spec is available in the Citrix ingress controller GitHub repo at: [gse-crd.yaml](https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/multicluster/Manifest/gse-crd.yaml)
 
 The GSE CRD is auto generated for an Ingress object if the service specified in the Ingress resource is referred in the GTP CRD instance and the `status-loadbalancer-ip/hostname` field is already populated. For a service of type `LoadBalancer`, the GSE CRD is auto generated if the service is referred in the GTP CRD instance and the `status-loadbalancer-ip/hostname` field is already populated.
 
 **Note:**
 For GSE CRD auto generation in the case of Ingress, host name should exactly match with the host name specified in the GTP CRD instance. For both Ingress and service of type `LoadBalancer`, the GSE CRD is generated only for the first port specified.
 
-## Deploy Citrix Multi-cluster ingress and load balancing solution
+## Deploy Citrix NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters
 
 ### Prerequisites**
 
@@ -223,7 +223,7 @@ Perform the following steps to deploy the Citrix global load balancing solution
 
           kubectl create -f  service-example.yaml
 
-     Following is a sample service.
+     The following is a sample service.
 
           apiVersion: v1
           kind: Service
@@ -243,7 +243,7 @@ Perform the following steps to deploy the Citrix global load balancing solution
               ingress:
               - ip: 10.102.217.72
 
-For a sample configuration of multi-cloud ingress and load balancing solution for Amazon EKS and Microsoft AKS clusters using Citrix ADC, see the [Multi-cloud and multi-cluster ingress and load balancing solution with Amazon EKS and Microsoft AKS clusters](../deploy/multi-cloud-ingress-lb-solution.md).
+For a sample configuration of multi-cloud ingress and load balancing solution for Amazon EKS and Microsoft AKS clusters using Citrix ADC, see the [Multi-cloud and NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters with Amazon EKS and Microsoft AKS clusters](../deploy/multi-cloud-ingress-lb-solution.md).
 
 ## How to direct the DNS resolution of pods to Citrix GSLB ADC
 
@@ -442,7 +442,6 @@ In a failover deployment, the application is deployed in multiple clusters and t
 
 The following example shows a sample GTP configuration for failover. Using the `primary` field, you can specify which cluster belongs to the active group and which cluster belongs to the passive group. The default value for the field is `True` indicating that the cluster belongs to the active group. You can use the `weight` field to direct more client requests to a specific cluster within a group than the other clusters if the configured method is round robin. The `monitor` parameter in the global traffic policy is used to configure the monitor in the Citrix ADC. The monitor can be bound to endpoints in each cluster to probe their health.
 
-
     apiVersion: "citrix.com/v1beta1"
     kind: globaltrafficpolicy
     metadata: