Release 1.19.6

Version 1.19.6

What's New

Support for alternate backends for OpenShift routes

When an OpenShift route is supported by multiple services, alternate backends are used for specifying the additional services.
Alternate backends for OpenShift routes are now supported by Citrix ingress controller. Citrix ADC is configured according to the weights provided in the routes definition and traffic is distributed among the service pods based on those weights. For more information, see Alternate Backend Support.

Enhancements

• Now, Citrix ingress controller supports binding default certificates in OpenShift routes.
• The default value for the environment variable NS_PROTOCOL is now changed to HTTPS and the default value for NS_PORT is now changed to 443.
• Earlier, front-end profiles for TCP, HTTP, and SSL were supported but the profile must be specified as part of a separate ingress called the front-end ingress. With this enhancement, you can specify front-end profiles as part of the regular ingress. This enhancement also helps to handle any conflicts that can arise from different ingresses belonging to the same content switching virtual server in a pre-determined way. For more information, see Configure HTTP, TCP, or SSL profiles on Citrix ADC.
• Now, Citrix ingress controller supports configuring global level front-end profiles for TCP, HTTP, and SSL using ConfigMap variables. Three new variables, FRONTEND_TCP_PROFILE, FRONTEND_HTTP_PROFILE, and FRONTEND_SSL_PROFILE, are added which can be used to set the front-end TCP, HTTP, and SSL profiles. For more information, see Configure HTTP, TCP, or SSL profiles on Citrix ADC.

Fixed issues

• In OpenShift routes, the targetPort field in the route represents the port of the pod. However, Citrix ingress controller was treating targtePort as a service port similar to the way it treats ingress. Hence, Citrix ingress controller was unable to handle destination services where targetPort is different from the service port. This issue is fixed now.