Skip to content
Was this article helpful?

Deploy Citrix ADC CPX as an Ingress device in Google Cloud Platform

This topic explains how to deploy Citrix ADC CPX as an ingress device in Google Kubernetes Engine (GKE)

Prerequisites

You should complete the following tasks before performing the steps in the procedure.

  • Ensure that you have a Kubernetes Cluster up and running.

  • If you are running your cluster in GKE, ensure that you have configured a cluster-admin role binding.

You can use the following command to configure cluster-admin role binding.

kubectl create clusterrolebinding citrix-cluster-admin --clusterrole=cluster-admin --user=<email-id of your google account>

You can get your Google account details using the following command.

gcloud info | grep Account

Deploy Citrix ADC CPX as an ingress device in Google Cloud Platform

  1. 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/gcp/manifest/apache.yaml

    Note

    In this example, apache.yaml is used. You should use the specific YAML file for your application.

  2. Deploy Citrix ADC 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/gcp/manifest/standalone_cpx.yaml

  3. Create the ingress resource using the following command.

    kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/gcp/manifest/cpx_ingress.yaml

  4. Create a service of type LoadBalancer for accessing the Citrix ADC CPX by using the following command.

    kubectl create -f https://raw.githubusercontent.com/citrix/citrix-k8s-ingress-controller/master/deployment/gcp/manifest/cpx_service.yaml

    Note

    This command creates a load balancer with an external IP for receiving traffic.

  5. 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 192.7.248.216 none 80/TCP 2m
    cpx-ingress LoadBalancer 192.7.241.6 pending 80:32258/TCP,443:32084/TCP 2m
    kubernetes ClusterIP 192.7.240.1 none 443/TCP 22h

  6. 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 192.7.248.216 none 80/TCP 3m
    cpx-ingress LoadBalancer 192.7.241.6 EXTERNAL-IP CREATED 80:32258/TCP,443:32084/TCP 3m
    kubernetes ClusterIP 192.7.240.1 none 443/TCP 22h

    Note

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

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

  1. Deploy a Citrix ADC CPX ingress with in built Citrix 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/gcp/manifest/all-in-one.yaml

  2. 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 following command:
    kubectl delete -f all-in-one.yaml

Was this article helpful?