-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Setting up service graph
Software requirements
| Kubernetes Distribution | Kubernetes Version | Container Network Interfaces (CNI) | CPX version | CIC version | Citrix ADM version | Citrix ADM Agent Version |
|---|---|---|---|---|---|---|
| Open source | v1.16.3 | Flannel, Calico, or Canal | 13.0–41.28 or later | 1.5.25 or later | 13.0–47.22 or later | 13.0–47.22 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 ADM, 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.
Before you begin
You can view service graph using the following scenarios:
-
Citrix ADM and Kubernetes cluster on the same network (for example, Citrix ADM and Kubernetes cluster hosted on the same Citrix Hypervisor).
-
Citrix ADM and Kubernetes cluster on a different network. In this scenario, you must configure an on-prem agent and register the agent on the network, where Kubernetes cluster is hosted.
Single tier or Unified ingress topology
Ensure that you have:
-
Configured Kubernetes cluster with single tier or unified ingress topology.
-
Added VPX, MPX, SDX, BLX instance in Citrix ADM and enabled Web Insight.
-
Added Kubernetes cluster in Citrix ADM.
Dual tier or Service Mesh Lite topology
Ensure that you have:
-
Configured Kubernetes cluster with any one of the supported topologies.
-
Configured static routes on Citrix ADM to enable communication between Citrix ADM and Citrix ADC CPX.
Note
You can ignore this procedure if you have deployed Citrix ADM 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 Citrix ADM.
-
Added a VPX, MPX, SDX, or BLX instance in Citrix ADM.
-
Added the Kubernetes cluster in Citrix ADM.
-
Deployed a sample microservice application.
-
Deployed Citrix ADC CPX and registered CPX to ADM (applicable only for two-tier architecture)
-
Enabled Auto-select Virtual Servers to license the virtual servers.
-
Enabled Web transaction and TCP transaction settings to All for Citrix ADM agent to get HTTP and TCP transactions.
-
Sent traffic to microservices.
Service mesh topology
Ensure that you have:
-
Configured Kubernetes cluster version
1.14.0with 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/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.
-
Configured static routes on Citrix ADM to enable communication between Citrix ADM and Citrix ADC CPX.
Note
You can ignore this procedure if you have deployed Citrix ADM 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 ADM.
-
Enabled Auto-select Virtual Servers to license the virtual servers.
-
Enabled Web transaction and TCP transaction settings to All for Citrix ADM agent to get HTTP and TCP transactions.
-
Sent traffic to microservices.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.