-
Low-touch onboarding of Citrix ADC instances using Citrix ADM service connect
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
-
-
-
Use ADM audit logs for managing and monitoring your infrastructure
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Setting up service graph
Software requirements
Kubernetes Distribution | Kubernetes Version | Container Network Interfaces (CNI) | CPX version | CIC version | Citrix ADM 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 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.
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 ADM and enabled Web Insight.
-
Added Kubernetes cluster in Citrix ADM.
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 a Citrix ADM agent and configured to enable communication between Citrix ADM and Kubernetes cluster or managed instances in your data center or cloud.
You can also deploy a Citrix ADM agent as a microservice. For more information, see the Install Citrix ADM Agent section in Getting Started.
-
Configured Static routes on Citrix ADM agent 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.
-
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 CPX 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 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 ADM agent and configured to enable communication between Citrix ADM and Kubernetes cluster or managed instances in your data center or cloud.
You can also deploy a Citrix ADM agent as a microservice. For more information, see the Install Citrix ADM Agent section in Getting Started.
-
Configured Static routes on Citrix ADM agent 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.
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.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.