Application Delivery Management

Manage the Kubernetes Ingress configuration in NetScaler Console

July 5, 2024

Contributed by:

R C

Kubernetes (K8s) is an open source container orchestration platform that automates the deployment, scaling, and management of cloud-native applications.

Kubernetes provides the Ingress feature which allows client traffic outside the cluster to access microservices of an application running inside the Kubernetes cluster. NetScaler instances can act as the Ingress to applications running inside a Kubernetes cluster. NetScaler instances can load balance and content route North-South traffic from the clients to any microservices inside the Kubernetes cluster.

Note

NetScaler Console supports the Ingress feature on the clusters with Kubernetes version 1.14–1.21.

NetScaler Console supports NetScaler VPX and MPX appliances as Ingress devices.

In the Kubernetes environment, the NetScaler instance load balances only the “NodePort” service type.

You can configure multiple NetScaler instances to act as Ingress devices on the same cluster or different clusters or namespaces. After you configure the instances, you can assign each instance to different applications based on the Ingress policy.

You can create and deploy an Ingress configuration using Kubernetes kubectl or APIs. You can also configure and deploy an Ingress from NetScaler Console.

You can specify the following aspects of Kubernetes integration in NetScaler Console:

Cluster – You can register or unregister Kubernetes clusters for which NetScaler Console can deploy Ingress configurations. When you register a cluster in NetScaler Console, specify the Kubernetes API server information. Then, select an agent that can reach the Kubernetes cluster and deploy Ingress configurations.
Policies – Ingress policies are used to select the NetScaler instance based on cluster or namespace to deploy an Ingress configuration. Specify the cluster, site, and instance information when you add a policy.

Before you begin

To use NetScaler instances as Ingress devices on Kubernetes clusters, ensure you have:

Kubernetes cluster in place.
Kubernetes cluster registered in NetScaler Console.

Configure the NetScaler Console with a secret token to manage a Kubernetes cluster

For NetScaler Console to be able to receive events from Kubernetes, you need to create a service account in Kubernetes for NetScaler Console. And, configure the service account with the necessary RBAC permissions in the Cluster.

Create a service account for NetScaler Console. For example, the service account name can be citrixadm-sa. To create a service account, see Use Multiple Service Accounts.
Use the cluster-admin role to bind the NetScaler Console service account. This binding grants a ClusterRole across the cluster to a service account. The following is an example command to bind a cluster-admin role to the service account.
```
kubectl create clusterrolebinding citrixadm-sa-admin --clusterrole=cluster-admin --serviceaccount=default:citrixadm-sa

```
After binding the NetScaler Console service account to the cluster-admin role, the service account has the cluster-wide access. For more information, see kubectl create clusterrolebinding.
Obtain the token from the created service account.

For example, run the following command to view the token for the citrixadm-sa service account:
```
kubectl describe sa citrixadm-sa

```
Run the following command to obtain the secret string of the token:
```
kubectl describe secret <token-name>

```

Add the Kubernetes cluster in NetScaler Console

After you configure a NetScaler agent and configure static routes, you must register the Kubernetes cluster in NetScaler Console.

To register the Kubernetes cluster:

Log on to NetScaler Console with administrator credentials.
Navigate to Orchestration > Kubernetes > Cluster. The Clusters page is displayed.
Click Add.
In the Add Cluster page, specify the following parameters:
1. Name - Specify a name of your choice.
2. API Server URL - You can get the API Server URL details from the Kubernetes main node.
  1. On the Kubernetes main node, run the command kubectl cluster-info.
  2. Enter the URL that displays for “Kubernetes master is running at.”
3. Authentication Token - Specify the authentication token string obtained while you configure NetScaler Console to manage a Kubernetes cluster. The authentication token is required to validate access for communication between the Kubernetes cluster and NetScaler Console. To generate an authentication token:
  1. On the Kubernetes main node, run the following commands:
    kubectl describe secret <token-name> 
  2. Copy the token that is generated and paste it as the Authentication Token
    
    For more information, see Kubernetes documentation.
4. Select the agent from the list.
5. Click Create.

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

Manage the Kubernetes Ingress configuration in NetScaler Console

July 5, 2024

Contributed by:

R C

July 5, 2024

Contributed by:

R C

Manage the Kubernetes Ingress configuration in NetScaler Console

Before you begin

Configure the NetScaler Console with a secret token to manage a Kubernetes cluster

Add the Kubernetes cluster in NetScaler Console

In this article