Release 1.9.9
Version 1.9.9
What's New
SSL certificate for services of type LoadBalancer through the Kubernetes secret resource
Earlier, the certificate for a service of type LoadBalancer with the SSL and SSL_TCP service type was specified using annotations. Now, certificates for front end and back end for a type LoadBalancer service can also be specified through the Kubernetes secret resource. Also, new annotations have been added to support a pre-configured certificate for the type LoadBalancer for front end and back end objects.
For more information, see SSL certificate for services of type LoadBalancer through the Kubernetes secret resource.
Fixed issues
-
Earlier the Citrix ingress controller was listening for continuous stream of deployment events which may build up memory and can delay the processing of ingress events in certain cases. With this feature, the Citrix ingress controller listens for deployment events and continuous deployment CRD events only if the
–enable-canaryargument is specified. -
Sometimes, the Citrix ingress controller was getting hung and it was not receiving any events. Now, timeouts are added so that the Citrix ingress controller can recover and reconnect if the connection with the Kubernetes API server gets hung.
-
Better optimisation in terms of processing Kubernetes deployment and secret events.
-
When the monitoring method is specified as HTTP in a global traffic policy (GTP) CRD instance, the Citrix multi-cluster GSLB controller was configuring the HTTP monitor, but not specifying the host header. With this fix, the host header is configured when the monitoring method is specified as HTTP.
Known issues
When you use the latest Citrix ADC CPX release (13.0.64.35) with the Citrix ingress controller, the UDP ingress feature is not working.
Helm chart specific changes
For Helm chart specific changes, see the Helm chart release notes.