NetScaler ingress controller

Deploy NetScaler GSLB Controller in OpenShift using NetScaler Operator

NetScaler Operator enables you to deploy NetScaler GSLB Controller in an OpenShift cluster. For information about GSLB, see GSLB overview and deployment topologies.

Deploy NetScaler GSLB Controller

Prerequisites

Steps to deploy NetScaler GSLB Controller using NetScaler Operator

Do the following steps:

  1. Navigate to Operators > Installed Operators and select NetScaler Operator.

    NetScaler Ingress Controller Operator

  2. Click the NetScaler GSLB Controller tab and click Create NetscalerGslbController.

    Create NetScaler GSLB Controller

    The NetScaler GSLB Controller instance YAML definition is displayed. Optionally, you can select Form view button and update the parameters in a form.

  3. Update the values for the required parameters in the displayed NetScaler GSLB Controller instance YAML and click Create. For information on the parameters that you need to configure, see the following table.

    NetScaler Ingress Controller Instance

    Parameter Description Mandatory/Optional
    gslbController
    image The NetScaler GSLB Controller image. Mandatory
    pullPolicy The NetScaler GSLB Controller image pull policy. Optional
    imagePullSecrets List of OpenShift secrets to be used for pulling the images from a private Docker registry or repository. For more information on how to create this secret, see Pull an Image from a Private Registry. Optional
    entityPrefix The prefixes for the resources on NetScaler VPX or NetScaler MPX. Mandatory
    acceptLicense Set yes to accept the GSLB Controller end user license agreement. Mandatory
    logLevel The log level to control the logs generated by NetScaler GSLB Controller. The supported log levels are: CRITICAL, ERROR, WARNING, INFO, DEBUG, TRACE, and NONE. For more information, see Logging. Optional
    openshift Set this argument if the OpenShift environment is being used. Mandatory
    disableAPIServerCertVerify Set this parameter to true for disabling API Server certificate verification. Optional
    kubernetesURL The kube-apiserver url that NetScaler GSLB Controller uses to register the events. If the value is not specified, NetScaler GSLB Controller uses the internal kube-apiserver IP address. Optional
    cleanupGSLBSiteConfig Set this parameter to true to clean up the GSLB site configuration. Optional
    LocalRegion Local region where the GSLB controller is deployed. Mandatory
    LocalCluster The name of the cluster in which the GSLB controller is deployed. This value is unique for each OpenShift cluster. Mandatory
    siteData[0].siteName The name of the first GSLB site configured in the GSLB device. Mandatory
    siteData[0].secretName The name of the secret that contains the login credentials of the first GSLB site. Mandatory
    siteData[0].siteIp IP address for the first GSLB site. Add the IP address of the NetScaler in site1 as siteData[0].siteIp. Mandatory
    sitedata[0].siteRegion The region of the first site. Mandatory
    sitedata[0].siteMask The netmask of the first GSLB site IP address. Mandatory
    sitedata[0].sitePublicIp The public IP address of the first GSLB Site. Mandatory
    sitedata[1].siteName The name of the second GSLB site configured in the GSLB device. Mandatory
    sitedata[1].secretName The secret containing the login credentials of the second site. Mandatory
    sitedata[1].siteIp IP address for the second GSLB site. Add the IP address of the NetScaler in site2 as siteData[0].siteIp Mandatory
    sitedata[1].siteRegion The region of the second site. Mandatory
    sitedata[1].siteMask The netmask of the second GSLB site IP address. Mandatory
    sitedata[1].sitePublicIp The public IP address of the second GSLB Site. Mandatory
    Parameter Description Mandatory/Optional
    netscaler
    nsIP NetScaler IP address. Mandatory
    adcCredentialSecret Secret required for the GSLB controller to connect to GSLB devices and push the configuration from the GSLB controller. Optional
    nsProtocol The protocol used by NetScaler GSLB Controller to communicate with NetScaler. You can also use HTTP on port 80. Optional
    nsPort The port used by NetScaler GSLB Controller to communicate with NetScaler. You can use port 80 for HTTP. Optional
    nitroReadTimeout The duration, in seconds, that NetScaler GSLB Controller has to wait to receive a response from NetScaler before terminating the connection. Optional
    Parameter Mandatory/Optional Description
    name Mandatory Name of the NetScaler GSLB Controller instance.
    acceptLicense Mandatory Set this value to Yes to accept the NetScaler GSLB Controller EULA.
    affinity Optional Affinity labels for pod assignment.
    nodeSelector Optional The node label key:value pair to be used for nodeSelector option in NetScaler GSLB Controller deployment.
    podAnnotations Optional Map of annotations to add to the pods.
    tolerations Optional The tolerations for the NetScaler GSLB Controller deployment.

    Notes:

    • If you want to configure more than two GSLB sites, include the details of all the GSLB sites in the siteData list as required.
    • You must specify either adcCredentialSecret or the combination of secretStore.username and secretStore.password to provide NetScaler VPX or NetScaler MPX credentials in the GSLB Controller instance YAML.
  4. Navigate to the Workloads > Pods section and verify whether the NetScaler GSLB Controller pod is up and running.

    Application Pod UP and Running

    Application Pod UP and Running

    Skip to References.

References

  • For information about deploying global traffic policy (GTP) and global service entry (GSE), see GTP and GSE deployment.
Deploy NetScaler GSLB Controller in OpenShift using NetScaler Operator