Skip to content

Release 1.25.6

Choose a tag to compare

View all tags
@sreejithgs sreejithgs released this 23 Jun 08:51
· 273 commits to master since this release
1.25.6
b7f27b5

Version 1.25.6

What's new

Consistent hashing algorithm support

Consistent hashing algorithms are mostly used for load balancing cache servers to achieve stateless persistency.
Consistent hashing can ensure that when a cache server is removed, only the requests cached in that specific server is rehashed and the rest of the requests are not affected.
You can now configure the consistent hashing algorithm on Citrix ADC using Citrix ingress controller.

For more information, see the consistent hashing algorithm support.

AppQoE support

You can configure the request-retry feature on Citrix ADC to forward the client request to the next available backend server whenever there is a connection failure to the backend server. Using the AppQoE CRD provided by Citrix, you can now configure request-retry policies on Citrix ADC with Citrix ingress controller. The AppQoE CRD enables the communication between the Citrix ingress controller and Citrix ADC for enforcing AppQoE policies.

For more information, see the AppQoE support documentation.

Enhancements

  • Citrix ingress controller logs are enhanced to indicate the missing subnet IP address (SNIP) information on Citrix ADC.
  • A new key service is added under the endpoint parameter for analytics configuration using ConfigMap. You can specify an IP address or service name of the Citrix ADC observability exporter service depending on whether the service is running on a virtual machine or as a Kubernetes service.
  • Now, you can configure the NS_NITRO_READ_TIMEOUT parameter to configure the Citrix ingress controller timeout for NITRO API calls. The default value for timeout is 20 seconds.

Fixed issues

  • Earlier, Citrix ingress controller was configuring services even when the service port information is incorrect in the Ingress resource definition. This issue is fixed now.

  • The functionality for logging packets to support observability was missing in the Ratelimit CRD. This issue is fixed now.

  • Ingress class for associating the rewrite and responder CRD to the ingress controller was missing. This issue is fixed now.

  • The servicenames section was made non-mandatory for the Auth CRD so that the Auth CRD can be referred via annotation in the Ingress.

Helm chart specific changes

For Helm chart-specific changes, see the Helm chart release notes.

Assets 2
Loading