Skip to content

v0.9.8-beta-2
Compare
Choose a tag to compare
@dheerajng dheerajng released this 28 Apr 10:14
· 14 commits to master since this release
v0.9.8-beta-2
494eaae
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Citrix xDS Adaptor v0.9.8-beta-2

What’s new

Enabling multiple xDS-Adaptors in a servicemesh to configure same Citrix ADC VPX/MPX

Earlier if multiple Citrix xDS-Adaptors in gateway mode were deployed in different namespaces of the servicemesh, and multiple xDS-adaptors configure the same Citrix ADC device, there used to be conflicts in configuration on Citrix ADC VPX/MPX. It used to happen as the name of frontend CS vserver and associated ADC config entities were created using listener name only. This could lead to name conflicts in ADC config.

Starting this release, when Citrix xDS-Adaptor is deployed in gateway mode, name of the frontend CS vserver generated by Citrix xDS-Adaptor includes unique vserver IP(VIP) provided to xDS-Adaptor in addition to listener name provided by xDS-server. This change ensures flawless deployment of multiple ingress/egress gateway pods in the same or different clusters and all pods configuring the same Citrix ADC device.

Fixed issues

The following issues are fixed in this release:

• Ingress/egress gateway pods can be deployed in namespaces labelled for CPX sidecar injection.

• Config optimization in gateway mode: Earlier Citrix ADC was configured for all clusters resources (CDS) in the mesh. This release ensures only relevant CDS resources are processed to configure Citrix ADC appropriately.

• SSL handshake failure between Citrix ADC ingress device and mTLS enabled services: If multiple mTLS enabled services were deployed in the mesh and exposed the same using Citrix ADC VPX/MPX ingress gateway, then sometimes there used to be SSL handshake failure between ingress device and sidecar CPX of the service.

Assets 6
Loading