NetScaler ingress controller

Deploy NetScaler CPX as an Ingress device in an Azure Kubernetes Service cluster

December 31, 2023

Contributed by:

This topic explains how to deploy NetScaler CPX as an ingress device in an Azure Kubernetes Service (AKS) cluster. NetScaler CPX supports both the Advanced Networking (Azure CNI) and Basic Networking (Kubenet) mode of AKS.

Note:

If you want to use Azure repository images for NetScaler CPX or the NetScaler Ingress Controller instead of the default quay.io images, then see Deploy NetScaler CPX as an Ingress device in an AKS cluster using Azure repository images.

Deploy NetScaler CPX as an ingress device in an AKS cluster

Perform the following steps to deploy NetScaler CPX as an ingress device in an AKS cluster.

Note:

In this procedure, Apache web server is used as the sample application.

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/azure/manifest/apache.yaml
```
Note:

In this example, apache.yaml is 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/azure/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/azure/manifest/cpx_ingress.yaml

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/azure/manifest/cpx_service.yaml
```
This command creates an Azure load balancer with an external IP for receiving traffic.

Verify the service and check whether the load balancer has created an external IP. Wait for some time if the external IP is not created.

kubectl  get svc

|NAME|TYPE|CLUSTER-IP|EXTERNAL-IP|PORT\(S)| AGE|
|----|----|-----|-----|----|----|
|apache |ClusterIP|10.0.103.3|none|   80/TCP | 2m|
|cpx-ingress |LoadBalancer |10.0.37.255 | pending |80:32258/TCP,443:32084/TCP |2m|
|Kubernetes |ClusterIP | 10.0.0.1 |none |  443/TCP | 22h |

Once the external IP for the load-balancer is available as follows, you can access your resources using the external IP for the load balancer.
```
kubectl  get svc

|NAME|TYPE|CLUSTER-IP|EXTERNAL-IP|PORT\(S)|  AGE|
|---|---|----|----|----|----|
|apache|ClusterIP|10.0.103.3 |none|80/TCP|  3m|
|cpx-ingress |LoadBalancer|10.0.37.255|  EXTERNAL-IP CREATED| 80:32258/TCP,443:32084/TCP |  3m|
|Kubernetes|    ClusterIP|10.0.0.1 |none| 443/TCP| 22h|
```
Note:

The health check for the cloud load-balancer is obtained from the readinessProbe configured in the NetScaler CPX deployment yaml file. If the health check fails, you should check the readinessProbe configured for NetScaler CPX. For more information, see readinessProbe and external Load balancer.

Access the application using the following command.

curl http://<External-ip-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/azure/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.yaml command.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Deploy NetScaler CPX as an Ingress device in an Azure Kubernetes Service cluster

December 31, 2023

Contributed by:

December 31, 2023

Contributed by:

Deploy NetScaler CPX as an Ingress device in an Azure Kubernetes Service cluster

Deploy NetScaler CPX as an ingress device in an AKS cluster

Quick Deploy

In this article