Release 1.21.9

Version 1.21.9

Enhancements

• Citrix ingress controller now supports WAF features such as request side streaming, configuring RFC profile, and grammar-based SQL injection detection support. For more information, see the example YAML file. See, configuring web application firewall policies for information on how to configure WAF.
• Previously Ingress status was updated with an external IP address only when Citrix ingress Controller is started with the –update-ingress-status argument configured as yes. Now, Ingress status is updated with an external IP address by default for tier-1 deployments. This argument –update-ingress-status configured as yes is required for tier-2 deployments with Citrix ADC CPX for updating the ingress status with external IPs.
• For multi-cluster Ingress, Citrix ingress controller now supports HTTPS monitors with SNI enabled by default during the TLS handshake.
• For multi-cluster Ingress, Citrix ingress controller now supports source IP persistence. For more information, see the multi-cluster ingress documentation.
• Citrix ingress controller feature-node-watch now supports OpenShift OVN CNI.

Fixed issues

• Earlier, OpenShift feature-node-watch was not configuring the correct routes on the Citrix ADC after the node modify event for OpenShift-SDN CNI. This issue is now fixed.
• Sometimes Listener CRD was failing to create cipher groups due to the name size limit of 39 characters. This issue is fixed by using the hash to limit the name size to 39 characters.
• The ingress.citrix.com/csvserver annotation was getting applied only when the first ingress belonging to the content switching virtual server is created. Now, this annotation gets applied regardless of the order of ingresses.
• In the Citrix ADC CPX BGP deployment, the service of type LoadBalancer status was not getting updated with external IP sometimes. This issue is fixed.
• Citrix ingress controller now supports the modification of service of type LoadBalancer by clearing the stale entries in Citrix ADC. This modification includes any port group and annotation modifications.
• While adding domain name servers through ConfigMap for tier 1 Citrix ADC, the existing domain name server configuration on Citrix ADC VPX was getting deleted if the existing configuration was not specified as part of the ConfigMap. Now, this issue is fixed.
• Earlier, When Citrix ingress controller was configuring existing alternate backend routes on OpenShift during boot-up, an error keyError: 'weighted_abpol' may occur. Now, it is fixed.