Setting up service graph
Software requirements
| Kubernetes Distribution | Kubernetes Version | Container Network Interfaces (CNI) | CPX version | CIC version | agent Version |
|---|---|---|---|---|---|
| Open source | v1.16.3 | Flannel, Calico, or Canal | 13.0–47.103 or later | 1.6.1 or later | 13.0–49.x or later |
You can configure the Kubernetes cluster with various deployment topologies and the following table provides the topologies that are supported in service graph:
| Topology | Supported in service graph |
|---|---|
| Single-Tier or Unified ingress | Yes |
| Dual-Tier | Yes |
| Cloud | Yes, but cloud load balancer is not shown in the graph |
| Service mesh lite | Yes |
| Service mesh | Yes |
| Services of type LoadBalancer | No |
| Services of type NodePort | No |
To complete setting up service graph in NetScaler Console, click the topology type that you have configured for your Kubernetes cluster and complete the mentioned procedures:
Note
The procedure to set up service graph for dual-tier and service mesh lite topologies remains the same.
Single tier or Unified ingress topology
Ensure that you complete the following steps to set up the single tier or unified ingress topology. For more information, see Detailed procedures to setup single tier or unified ingress topology.
-
Configured Kubernetes cluster with single tier or unified ingress topology.
-
Added VPX, MPX, SDX, BLX instance in NetScaler Console and enabled Web Insight.
-
Added Kubernetes cluster in NetScaler Console.
Dual tier or Service Mesh Lite topology
Ensure that you complete the following steps to set up the dual tier or service mesh lite topology. For more information, see Detailed procedures to setup dual tier or service mesh lite topology.
-
Configured Kubernetes cluster with any one of the supported topologies.
-
Installed an agent and configured to enable communication between NetScaler Console and Kubernetes cluster or managed instances in your data center or cloud.
You can also deploy an agent as a microservice. For more information, see the Install a NetScaler agent section in Getting Started.
-
Configured Static routes on the agent to enable communication between NetScaler Console and NetScaler CPX.
Note
You can ignore this procedure if you have deployed an agent as a microservice in the same cluster.
-
Downloaded the sample deployment files from GitHub repository.
-
Added required parameters in CPX YAML file to ensure successful CPX registration with NetScaler Console.
-
Added a VPX, MPX, SDX, or BLX instance in NetScaler Console.
-
Added the Kubernetes cluster in NetScaler Console.
-
Deployed a sample microservice application.
-
Deployed NetScaler CPX and registered CPX to NetScaler Console (applicable only for two-tier architecture).
-
Enabled Web transaction and TCP transaction settings to All for the agent to get HTTP and TCP transactions.
-
Sent traffic to microservices.
Service mesh topology
Ensure that you complete the following steps to set up the service mesh topology. For more information, see Detailed procedures to setup service mesh topology.
-
Configured Kubernetes cluster version
1.14.0with any one of the following service mesh topologies:-
NetScaler CPX as a sidecar proxy for Istio
-
NetScaler as an Ingress Gateway for Istio
For more information, see NetScaler Istio Adapter deployment architecture
-
-
Enabled
admissionregistration.k8s.io/v1beta1API. You can verify the API by using:kubectl api-versions | grep admissionregistration.k8s.io/v1beta1The following output indicates that the API is enabled:
admissionregistration.k8s.io/v1beta1 -
Installed Istio
istio v.1.3.0. -
Installed Helm version 3.x.
-
Installed an agent and configured to enable communication between NetScaler Console and Kubernetes cluster or managed instances in your data center or cloud.
You can also deploy an agent as a microservice. For more information, see the Install a NetScaler agent section in Getting Started.
-
Configured Static routes on the agent to enable communication between NetScaler Console and NetScaler CPX.
Note
You can ignore this procedure if you have deployed NetScaler agent as a microservice in the same cluster.
-
Configured the required parameters to populate the service mesh topology data.
-
Deployed a sample application.
-
Added the Kubernetes cluster in NetScaler Console.
-
Enabled Web transaction and TCP transaction settings to All for the agent to get HTTP and TCP transactions.
-
Sent traffic to microservices.
After you complete the required setup procedures, you can view service graph populated at Applications > Service Graph and in the Microservices tab. For more information, see Service Graph details.