Citrix ingress controller version 1.9.20

Helm chart release notes for the Citrix ingress controller version 1.9.20

This release note contains information about the Helm chart related changes for the Citrix ingress controller version 1.9.20.

What's New

• Names for the following parameters are changed and now the names are generated.

  • Deployment
  • ClusterRole
  • ClusterRoleBinding
  • ServiceAccount
  • Services
  • ConfigMap

Known Issues

You cannot perform a Helm upgrade from older Citrix ingress controller versions to 1.9.20 version. You need to perform a new installation for the Citrix ingress controller version 1.9.20.

Citrix ingress controller version 1.9.9

Helm chart release notes for the Citrix ingress controller version 1.9.9

This release note contains information about the Helm chart related changes for the Citrix ingress controller version 1.9.9.

What's New

• The following parameters were changed:

  Old parameter name	New name
  defaultSSLCert	defaultSSLCertSecret
  loginFileName	adcCredentialSecret
  nsNamespace	entityPrefix

• A new parameter cicSettings is added which makes updating new ConfigMaps easier.

• A new argument --update-ingress-status is added.

• By default crds.install is now set as false.

• WAF CRDs are now supported.

• The separate parameter for the image tag was removed from all Helm charts.

• For Citrix ADC CPX with the Citrix ingress controller deployment:

  • Support for non-default password for Citrix ADC CPX

  • Citrix ADC CPX version is changed to 13.0-64.35

• Chart specific changes:

  • Citrix node controller (CNC) charts: loginFileName is changed to adcCredentialSecret.

  • Multi-cluster ingress Charts:

    The following parameter names are changed:

    • loginFileName is changed to adcCredentialSecret
    • nsNamespace is changed to entityPrefix

Known Issues

You cannot perform a Helm upgrade from the Citrix ingress controller version 1.9.2 to 1.9.9. You need to perform a new installation for the Citrix ingress controller version 1.9.9.

citrix-istio-adaptor v1.2.0-beta

Citrix-istio-adaptor Version 1.2.0-beta

What’s new

Support for HTTP mirroring

Traffic mirroring provides a way to minimize the risk in bringing your application changes to production. Instead of routing production traffic to a newly deployed service, you can send a copy of the production traffic to a mirrored service. You can then observe the service that is receiving mirrored traffic for errors.

Citrix istio-adaptor now supports HTTP Traffic Mirroring. [NSNET-13891]

Support for Weighted Service Entry

A service entry describes the properties of a service (DNS name, VIPs, ports, protocols, endpoints). Using a weighted service entry, you can associate a load balancing weight with an endpoint. Endpoints with higher weights receive proportionally high traffic compared to endpoints with lower weights.

Citrix istio-adaptor now supports Weighted Service Entries. [NSNET-13514])

Support for Desired State API

Service group configuration on a Citrix ADC appliance requires frequent updates depending on the scale requirements or runtime changes to application servers. You can use desired state API and accept the intended member set for a service group in a single API and effectively update the configuration. Usage of desired state API improves the performance of updating servicegroup members significantly.

Citrix istio-adaptor now supports Desired State APIs. [NSNET-12761]

Integration with Citrix Observability Exporter

Now, you can integrate a Citrix ADC deployed as an Istio sidecar with Citrix Observability Exporter. Using Citrix Observability Exporter, you can export metrics and transactions from Citrix ADCs to desired endpoints such as Zipkin and Prometheus and analyze them to get valuable insights. [NSNET-11533]