Avi Kubernetes Operator Version 1.4 Release Notes
The Avi Vantage platform integration with OpenShift/ Kubernetes provides a redesigned architecture involving a new operator called Avi Kubernetes Operator (AKO). The following illustration outlines the components of the Avi Kubernetes integration.
What’s New in AKO Version 1.4.1
Support for shared L4 VIP across multiple service of type
Option to add global FQDN for a hostname via Host Rule
Temporary support for HTTP Caching for secure ingresses/routes via Pool objects
Option to use dedicated Virtual Service per Ingress hostname
Persistence profile in HTTPRule CRD
Extended Virtual Hosting support for Avi Enterprise License
Note: Enhanced Virtual Hosting is currently under Tech Preview.
Key Changes in AKO 1.4.1
- The field
networkNamein values.yaml is changed to
- AKO qualification for Kubernetes 1.19, 1.20, 1.21
End of Support
namespacesharding is deprecated starting from AKO version 1.4
Known Issues in AKO 1.4.1
- With Avi Controller version 20.1.4, there are restrictions on the length of pool object names in the Controller. To comply with this change, the namespace/hostname/ingress names have to be adjusted accordingly. The current restriction on the controller is 128 characters with 119 characters being usable.
- The current restriction on the number of DNS records supported per shared virtual service is 1000 on the Avi Controller. Hence if the shard size is chosen as SMALL, then the collective DNS records (hostnames) in a cluster must be less than 1000 for layer 7 ingress.
- If a Hostrule CRD is used to program a GSLB FQDN in AKO that maps to a secure local FQDN, a redirect rule is not added for the GS FQDN.
- In EVH mode, status IP updates could be inconsistent if multiple Ingresses share the same hostname.
Document Revision History
|April 28, 2021||Published the Release Notes for AKO version 1.4.1|