Skip to content

Release 1.13.15

Choose a tag to compare

View all tags
@sreejithgs sreejithgs released this 01 Feb 10:13
· 669 commits to master since this release
1.13.15
940d5cd

Version 1.13.15

What's New

Policy based routing

When you are using a single Citrix ADC to load balance multiple Kubernetes clusters, the Citrix ingress controller adds static routes to establish connectivity between Citrix ADC and Kubernetes pods. However, when the pod CIDRs overlap there may be route conflicts. Using policy based routing you can route packets based on a specified criteria and avoid such route conflicts.

For more information, see the policy based routing documentation.

Simple canary with Ingress annotations

Canary release is a technique to reduce the risk of introducing a new software version in production by first rolling out the change to a small subset of users. Canary deployment is already supported using the Canary CRD. Now, Citrix also provides a simpler option for canary deployment using Ingress annotations. For more information, see the simple canary with Ingress annotations documentation.

Call Home enablement for the Citrix Ingress controller in Citrix ADC

The Call Home feature gathers information about the performance of a product and uploads them to a Citrix server which helps Citrix to diagnose issues and resolve them. Now, the Call Home feature available on Citrix ADC can be enabled for the Citrix ingress controller deployments. For more information, see the Call Home enablement for the Citrix ingress controller documentation.

Support for HTTP and HTTPs URL sources for OAS documents

Earlier, only Open API Specification (OAS) documents hosted in Git repositories were supported by the API Gateway CRD. Now, API Gateway CRD can also fetch OpenAPI Specification (OAS) documents from non-Git sources such as HTTP or HTTPs URLs. For more information, see Deploy API gateway using GitOps.

Ingress V1 enhancements and IngressClass support

With the Kubernetes version 1.19, the Ingress resource is generally available. As a part of this change, a new resource named as IngressClass is added to the ingress API. Using this resource, you can associate Ingress resources to specific Ingress controllers. Now, the Citrix ingress controller supports Ingress V1 enhancements and the IngressClass resource.

For more information, see the Ingress class support documentation.

Enhancements

The following environment variables are added in this release to the Citrix ingress controller:

  • POD_IPS_FOR_SERVICEGROUP_MEMBERS: By default while configuring services of type LoadBalancer and NodePort on an external tier-1 Citrix ADC, the Citrix ingress controller adds NodeIP and NodePort as service group members. If this variable is set as True, pod IP address and port are added instead of NodeIP and NodePort as service group members.

  • IGNORE_NODE_EXTERNAL_IP: While adding NodeIP for services of type LoadBalancer or NodePort on an external tier-1 Citrix ADC, the Citrix ingress controller prioritizes an external IP address over an internal IP address. When you want to prefer an internal IP address over an external IP address for NodeIP, you can set this variable to True.

Fixed issues

  • Now, the --feature-node-watch argument is supported for Calico CNI.

  • Earlier adding a certificate to the Citrix ADC may occasionally fail due to the presence of a stale intermediate CA certificate. Now, the Citrix ingress controller retries to add the certificate after deleting the intermediate CA certificate.

  • When you delete OpenShift routes, the Citrix ingress controller may raise an exception. This issue is fixed now.

Assets 2
Loading