Skip to content

Release 1.9.2
Compare
Choose a tag to compare
@sreejithgs sreejithgs released this 25 Aug 05:54
· 822 commits to master since this release
1.9.2
0123a05

Version 1.9.2

What's New

Multi-cluster ingress and load balancing solution using the Citrix ingress controller

Citrix provides a multi-cluster ingress and load balancing solution which globally monitors applications, collect, and share metrics across different clusters, and provides intelligent load balancing decisions. It ensures better performance and reliability for your Kubernetes services that are exposed using Ingress or using type LoadBalancer.

For more information, see Multi-cluster ingress and load balancing solution using the Citrix ingress controller.

Configuring web application firewall policies with the Citrix ingress controller

Now, you can configure the web application firewall policies with the Citrix ingress controller on the Citrix ADC using the WAF CRD. The WAF CRD enables communication between the Citrix ingress controller and Citrix ADC for enforcing web application firewall policies in a Kubernetes environment.

For more information, see Configuring web application firewall policies with the Citrix ingress controller

Support for cookie based persistence configuration using ConfigMap

You can now enable cookie based persistence configuration using ConfigMap.
For more information, see ConfigMap support for the Citrix ingress controller.

Authorization policy support

The Citrix ingress controller now supports configuring authorization policies on Citrix ADCs using the Citrix Auth CRD.
For more information, see Define authentication policies on the Ingress Citrix ADC.

Fixed issues

  • Earlier, when a service type is changed from ClusterIP or NodePort to LoadBalancer, the IP address was not allocated by the Citrix IPAM controller for the service of type LoadBalancer. Now, the IP address is allocated to the service of type LoadBalancer when you change the type of service. You can change the service type using the kubectl patch command.

  • Automatic static route configuration of the associated Ingress device using the feature-node-watch argument was not supported in OpenShift deployments. Now, automatic static route configuration is supported.

  • Earlier, the Citrix ingress controller was failing for endpoints which do not have information about backing pods while using LoadBalancer type of services. With this fix, the Citrix ingress controller handles endpoints with no backing pod information correctly.

Assets 2
Loading