Release 1.23.10

Version 1.23.10

What's new

Listener CRD support for Ingress using annotations

Citrix ingress controller already provides content routing CRDs such as the Listener CRD for front-end configurations and HTTProute for back-end routing logic. Now, Listener CRD can be applied for Ingress resources using an annotation provided by Citrix. Through this feature, you can use the Listener CRD for your Ingress resource and separate the creation of the front-end configuration from the Ingress definition. Hence, NetOps can separately define the Listener resource to configure front-end IP, certificates, and other front-end parameters (TCP, HTTP, and SSL). Any configuration changes can be applied to the listener resources without changing each Ingress resource.

For more information, see Listener CRD support for Ingress using annotation.

Support for setting log format as JSON

Now, you can view Citrix ingress controller log messages in JSON format. For more information, see ConfigMap support.

Fixed issues

• Earlier, if an Ingress resource and an OpenShift route have the same name and the OpenShift route does not belong to a valid route sharding then the ingress resource was getting unconfigured. This issue is fixed now.

• When a service of the type LoadBalancer was modified and the IPAM controller was used for the IP address configuration, Citrix ingress controller was repeatedly configuring and unconfiguring the service earlier. This issue is fixed now

• Earlier, while deploying the latest version of the multi-cluster ingress controller the following error was getting displayed:
  AttributeError: 'IngressCRDInstance' object has no attribute 'listener_mode'. Now, this issue is fixed.

• When Citrix ADC was rebooting, the following traceback was getting displayed earlier:
  TypeError: ‘NoneType’ object is not iterable. Now, this issue is fixed.

• After the re-creation of Ingress, CRD policies were not getting bound to load balancing virtual servers. This issue is now fixed.