NetScaler ingress controller

Service class for services of type LoadBalancer

When services of type LoadBalancer are deployed, all such services are processed by the NetScaler Ingress Controller and configured on NetScalers. However, there may be situations where you want to associate only specific services to a NetScaler Ingress Controller if multiple Ingress controllers are deployed.

For Ingress resources this functionality is already available using the Ingress class feature. Similar to the Ingress class functionality for Ingress resources, service class functionality is now added for services of type LoadBalancer.

You can associate a NetScaler Ingress Controller with multiple service classes using the --service-classes argument under the spec section of the YAML file. If a service class is not specified for the ingress controller, then it accepts all services of the type LoadBalancer irrespective of the presence of the service.citrix.com/class annotation in the service.

If the service class is specified to the NetScaler Ingress Controller, then it accepts only those services of the type LoadBalancer that match the service.citrix.com/class annotation. In this case, the NetScaler Ingress Controller does not process a type LoadBalancer service if it is not associated with the service.citrix.com/class annotation.

Sample YAML configurations with service classes

Following is a snippet from a sample YAML file to associate service-classes with the Ingress Controller. In this snippet, the following service classes are associated with the Ingress Controller.

svc-class1
svc-class2

spec:
serviceAccountName: cic-k8s-role
containers:
- name: cic-k8s-ingress-controller
  # specify the service classes to be supported by NetScaler Ingress Controller in args section.
  # First line should be --service-classes, and every subsequent line should be
  # the name of allowed service class. In the given example two classes named
  # "svc-class1" and "svc-class2" are accepted. This will be case-insensitive.
  args:
    - --service-classes
      svc-class1
      svc-class2
<!--NeedCopy-->

Following is a snippet from a type LoadBalancer service definition YAML file where the service class association is depicted. In this example, an Apache service is associated with the service class svc-class1. If the NetScaler Ingress Controller is configured to accept svc-class1, it configures the service on the NetScaler.

apiVersion: v1
kind: Service
metadata:
     name: apache
     annotations:
         service.citrix.com/class: 'svc-class1'
     labels:
        name: apache
spec:
   type: LoadBalancer
   selector:
       name: apache
   ports:
   - name: http
     port: 80
     targetPort: http
   selector:
   app: apache
<!--NeedCopy-->

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

Service class for services of type LoadBalancer

Service class for services of type LoadBalancer

Sample YAML configurations with service classes

In this article