-
-
SSL certificate for services of type LoadBalancer through the Kubernetes secret resource
-
BGP advertisement for type LoadBalancer services and Ingresses using NetScaler CPX
-
NetScaler CPX integration with MetalLB in layer 2 mode for on-premises Kubernetes clusters
-
Advanced content routing for Kubernetes Ingress using the HTTPRoute CRD
-
IP address management using the NetScaler IPAM controller for Ingress resources
-
Deploy NetScaler ingress controller for NetScaler with admin partitions
-
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!
Deploy NetScaler CPX as an Ingress device in Elastic Kubernetes Service (EKS)
This topic explains how to deploy NetScaler CPX as an ingress device in Elastic Kubernetes Service (EKS) clusters.

Deploy NetScaler CPX as an ingress device in Elastic Kubernetes Service (EKS)
-
Deploy the required application in your Kubernetes cluster and expose it as a service in your cluster using the following command.
kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/aws/manifest/apache.yamlNote:
In this example,
apache.yamlis used. You should use the specific YAML file for your application. -
Deploy NetScaler CPX as an ingress device in the cluster using the following command.
kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/aws/manifest/standalone_cpx.yaml -
Create the ingress resource using the following command.
kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/aws/manifest/cpx_ingress.yamlAn Ingress class named citrix-ingress is used in this example. Please see our detailed Ingress class documentation.
-
Create a service of type LoadBalancer for accessing the NetScaler CPX by using the following command.
kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/aws/manifest/cpx_service.yamlNote:
This command creates a load balancer with an external IP/Hostname for receiving traffic.
-
Verify the service and check whether the load balancer has created an external IP address or hostname.
kubectl get svc cpx-ingress |NAME | TYPE | CLUSTER-IP | EXTERNAL-IP | PORT\(S) | AGE | | --- | ---| ----| ----| ----| ----| |cpx-ingress |LoadBalancer | 10.7.241.6 | EXTERNAL-HOSTNAME | 80:32258/TCP,443:32084/TCP | 2m| -
Access the application using the following command.
curl http://<External-hostname-of-loadbalancer>/ -H 'Host: citrix-ingress.com'
Quick Deploy
For the ease of deployment, you can just deploy a single all-in-one manifest that would combine the steps explained in the previous topic.
-
Deploy a NetScaler CPX ingress with in built NetScaler Ingress Controller in your Kubernetes cluster using the all-in-one.yaml.
kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/aws/manifest/all-in-one.yaml -
Access the application using the following command.
curl http://<External-ip-of-loadbalancer>/ -H 'Host: citrix-ingress.com'Note:
To delete the deployment, use the
kubectl delete -f all-in-one.yamlcommand.
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.