Avi Kubernetes Operator Version 1.2 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.
Issues Resolved in AKO version 1.2.3
- AV-99789: HTTP Rule does not get applied to Pools for nested paths of type
Issues Resolved in AKO version 1.2.2
- AV-99538: AKO pod crashed when Ingress is configured with no backends
What’s New in AKO Version 1.2.1
Support for pod network connectivity via static routing in OpenShift
Support for Avi Controller release 20.1.1
Key Changes in AKO 1.2.1
The AKO pod restarts if it is unable to establish a connection after retries with the Avi Controller on the first boot-up.
The AKO pod uses a stateful sets instead of an earlier deployment yaml to ensure that the two AKO pods do not run simultaneously at a given point in time.
VRF based routing support with AKO has been deprecated
Pod Security Policies for the AKO pod are provided in 1.2.1
End of Support
VRF based Static Routing for Pod Connectivity
Deprecated the need for having clusters in different VRFs.
Starting with AKO 1.2.1, all static routes are created in global VRF.
Pod connectivity is now available through SE groups per Kubernetes/OpenShift cluster.
To install AKO and get started, refer to the AKO Installation Guide.
For more information about AKO, refer to the Documentation for AKO.
To know more about the compatibility matrix for the Avi Controller, AKO, Kubernetes, and Kubernetes CNIS, refer to the Compatibility Guide for AKO.
Document Revision History
|September 18, 2020||Published the Release Notes for AKO version 1.2.1|
|July 20, 2020||Published the Release Notes for AKO version 1.2.1|