NetScaler ingress controller

Entity name change

December 31, 2023

Contributed by:

While adding the NetScaler entities, the NetScaler Ingress Controller maintains unique names per Ingress, service or namespace. Sometimes, it results in NetScaler entities with large names even exceeding the name limits in NetScaler.

Now, the naming format in the NetScaler Ingress Controller is updated to shorten the entity names. In the updated naming format, a part of the entity name is hashed and all the necessary information is provided as part of the entity comments.

After this update, the comments available on lbvserver and servicegroup entity names provides all the necessary details like the ingress name, ingress port, service name, service port, and the namespace of the application.

Format for comments

Ingress: ing:<ingress-name>,ingport:<ingress-port>,ns:<k8s-namespace>,svc:<k8s-servicename>,svcport:<k8s-serviceport>

Service of type LoadBalancer: lbsvc:<k8s-servicename>,svcport:<k8s-serviceport>,ns:<k8s-namespace>

The following table explains the entity name changes introduced with the NetScaler Ingress Controller version 1.12.

Entity	Old naming format	New naming format	Description/Comments
`csvserver` (ingress)	`k8s-192.2.170.67_80_http`	`k8s-192.2.170.67_80_http`	no changes
`csvserver` (`type LoadBalancer`)	`k8s-apache_default_80_svc`	`k8s-apache_80_default_svc`	Now, the port is followed by a namespace
`lbvserver` (`type LoadBalancer`)	`k8s-apache_default_80_svc_k8s-apache_default_80_svc`	`k8s-apache_80_lbv_wlikeqxno5vunbthsoj4lxegk7cddh6p` Comment: `lbsvc:apache,svcport:80,ns:default`	The comment for `type LoadBalancer` is now different
`servicegroup` (`type LoadBalancer`)	`k8s-apache_default_80_svc_k8s-apache_default_80_svc`	`k8s-apache_80_sgp_wlikeqxno5vunbthsoj4lxegk7cddh6p`	The suffix `sgp` is added
`cspolicy` or `csaction` or `responder policy`	`k8s-web-ingress_default_443_k8s-frontend_default_80_svc`	`k8s-frontend_80_csp_267pneiak5rw6hoygvrqrzpm4k6thz2p`	Moved service-name, service-port to the beginning, added suffix of cs, hashed ingress-name, ingress-port, and namespace
`lbvserver` (ingress)	`k8s-web-ingress_default_443_k8s-frontend_default_80_svc`	`k8s-frontend_80_lbv_267pneiak5rw6hoygvrqrzpm4k6thz2p` Comment: `ing:web-ingress,ingport:5080,ns:default,svc:frontend,svcport:80`	Suffix `lbv` and comment added to the entity
`servicegroup` (ingress)	`k8s-web-ingress_default_443_k8s-frontend_default_80_svc`	`k8s-frontend_80_sgp_267pneiak5rw6hoygvrqrzpm4k6thz2p`	Suffix `sgp` is added.
`lbvserver` (UDP)	`k8s-web-ingress_default_9053-udp_k8s-bind_default_53-udp_svc`	`k8s-bind_53-udp_lbv_uyomblblagixrtw3cxrf23tak6wkpfmw`	`-udp` is still appended to the port as earlier.

When you upgrade from an older version of the NetScaler Ingress Controller to the latest version, the NetScaler Ingress Controller renames all the entities with the new naming format. However, the NetScaler Ingress Controller does not handle the downgrade from the latest version to an older version.

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

Entity name change

December 31, 2023

Contributed by:

December 31, 2023

Contributed by:

Entity name change

Format for comments

In this article