Setting up service graph 编辑

Setting up service graph

Software requirements

Kubernetes DistributionKubernetes VersionContainer Network Interfaces (CNI)CPX versionCIC versionCitrix ADM Agent Version
Open sourcev1.16.3Flannel, Calico, or Canal13.0–47.103 or later1.6.1 or later13.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:

TopologySupported in service graph
Single-Tier or Unified ingressYes
Dual-TierYes
CloudYes, but cloud load balancer is not shown in the graph
Service mesh liteYes
Service meshYes
Services of type LoadBalancerNo
Services of type NodePortNo

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.

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 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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:41 次

字数:13204

最后编辑:8年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文