Skip to content

Release 1.14.17

Choose a tag to compare

View all tags
@sreejithgs sreejithgs released this 01 May 16:05
· 596 commits to master since this release
1.14.17
a83dd51

Version 1.14.17

What's New

Advanced content routing for Ingress using the HTTPRoute CRD

Now, Citrix supports configuring the HTTP route CRD resource as a resource backend in Ingress. By default, Ingress supports only limited content routing capabilities like path and host based routing. Using this feature, you can extend advanced content routing capabilities to Ingress and perform content switching based on query parameters, cookies, HTTP headers, and other Citrix ADC custom expressions.

For more information, see the Advanced content routing for Ingress using the HTTPRoute CRD documentation.

IP address management using the Citrix IPAM controller for Ingress resources

For service of type LoadBalancer, you can automatically allocate IP addresses to services from a specified IP address range using the IPAM controller. Now, this functionality is extended to ingress resources as well. When the virtual IP address (VIP) is not specified for an Ingress resource and the IPAM controller is enabled, it allocates an IP address for the ingress resource from a specified range. The Citrix ingress controller configures the allocated IP address as a VIP in Citrix ADC MPX or VPX.
For more information, see the IP address management using the Citrix IPAM controller for Ingress resources documentation.

Authentication support with the content routing CRD

Authentication support is now extended with content routing CRD, where content routing CRDs are supported for configuring advance policies.
For more information, see the Auth CRD documentation.

IPSET support

An IPSET is a set of IP addresses, which are configured on the Citrix ADC appliance as Subnet IP addresses (SNIPs) or VIPs. Now, you can specify the name of the IPSET while configuring the content switching virtual server on a Citrix ADC using the Citrix ingress controller.

For more information, see the Annotation documentation.

Profile support for the Listener CRD

For HTTP, TCP, or SSL protocols, you can group a set of configurations specific to a protocol as a profile and apply it on the Citrix ADC. Now, HTTP, TCP, and SSL profiles are supported for the Listener CRD. The Listener CRD also supports the analytics profile which enables to export the transaction data to Citrix observability exporter.
For more information, see the Profile support for the Listener CRD documentation.

Fixed issues

  • After a reboot of the Citrix ingress controller on the OpenShift platform, Citrix ADC entities like the content switching virtual server were deleted and re-created on the Citrix ADC. This issue is now fixed.

  • While enabling some features in Citrix ADC, it may throw a NITRO exception with the error code 1097. This issue is fixed.

  • Ingress with the version networking.k8s.io/v1 was not getting configured in the Amazon EKS cluster. This issue is fixed.

  • While adding the Citrix observability exporter server, Citrix ADC may throw a NITRO exception with the error code 1335. This issue is fixed.

  • While adding the Citrix ingress controller string map, Citrix ADC was throwing a NITRO exception due to the presence of "-" in the Kubernetes namespace. This issue is fixed in this release.

Known issues

A stand-alone Citrix ingress controller for configuring Citrix ADC VPX or MPX raises an exception when an ingress resource it supports has neither the frontend-ip annotation nor an ipam-range annotation. This issue has no functionality impact.

Assets 2
Loading