Setting up service graph

Software requirements

Kubernetes Distribution Kubernetes Version Container Network Interfaces (CNI) CPX version CIC version Citrix Application Delivery and Management 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 Citrix Application Delivery and Management, 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 Citrix Application Delivery and Management and enabled Web Insight.

  • Added Kubernetes cluster in Citrix Application Delivery and Management.

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.

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.0 with any one of the following service mesh topologies:

    • Citrix ADC CPX as a sidecar proxy for Istio

    • Citrix ADC as an Ingress Gateway for Istio

    For more information, see Citrix ADC Istio Adapter deployment architecture

  • Enabled admissionregistration.k8s.io/v1beta1 API. You can verify the API by using:

    kubectl api-versions | grep admissionregistration.k8s.io/v1beta1

    The 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 a Citrix Application Delivery and Management agent and configured to enable communication between Citrix Application Delivery and Management and Kubernetes cluster or managed instances in your data center or cloud.

    You can also deploy a Citrix Application Delivery and Management agent as a microservice. For more information, see the Install Citrix Application Delivery and Management Agent section in Getting Started.

  • Configured Static routes on Citrix Application Delivery and Management agent to enable communication between Citrix Application Delivery and Management and Citrix ADC CPX.

    Note

    You can ignore this procedure if you have deployed Citrix Application Delivery and Management 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 Citrix Application Delivery and Management.

  • Enabled Auto-select Virtual Servers to license the virtual servers.

  • Enabled Web transaction and TCP transaction settings to All for Citrix Application Delivery and Management 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.

Setting up service graph