Release version 1.32.7
What's new
NetScaler provides a kubectl plug-in “netscaler-k8s” to inspect ingress controller deployments and aids in troubleshooting operations. You can inspect NetScaler config and related Kubernetes components using the subcommands available with this plug-in.
For more information, see the NetScaler kubectl plugin repository.
Fixed issues
- If an Ingress resource refers to the Listener resource, content-switching policies were getting disassociated from the content-switching virtual server after the Citrix ingress controller restart. This issue is fixed now.
- There was an erroneous entry for
device_fingerprintin the BOT CRD definition due to which BOT CRDs were not getting applied. This issue is fixed now.
Enhancements
- Citrix ingress controller now supports multiple response codes in the GTP CRD. Earlier only one response code was allowed in the GTP CRD.
- Citrix ingress controller deployed with the scope
namespaceis now enhanced to process CRDs in the local namespace. Earlier, it was only supporting Ingress resources.
Note:
You must recreate the BOT CRD instance as per the new definition.