Compatibility Guide for AKO
The Avi Vantage platform integrates with Kubernetes/OpenShift using the operator called Avi Kubernetes Operator (AKO). This document outlines the compatibility and features supported by AKO in different environments.
Support for Kubernetes/ Orchestrators
The AKO version 1.2.1 support for Kubernetes/Orchestrators is as below:
|AKO Release||Versions Supported|
|Kubernetes Support||Versions 1.16, 1.17, 1.18|
|OpenShift Support||Versions 4.3, 4.4, 4.5|
Support for Avi Ecosystems and CNI
Note: The above table lists the minimum supported AKO version for each combination.
Avi Controller Version Support for AKO
|AKO Release(s)||Avi Controller Versions Supported|
|0.9||118.2.6 - 18.2.10|
|1.1||18.2.6 - 18.2.10|
|1.2||18.2.10, 20.1.1 (minimum requirement)|
Features Not Supported in AKO Release 1.2.1
AKO version 1.2.1 does not support the following:
- OpenShift 3.x
- Avi Annotations
- Egress pod
- Multiple tenants
Caveats and Restrictions
Static Routing for Pod connectivityis enabled, then upgrade from AKO version 1.1 to version 1.2 is not supported. In this case, delete the existing environment in version 1.1.1 and install AKO version 1.2.
- AKO does not support ingresses which do not have either hostname or a path defined.
- Ingresses in Kubernetes will be deployed only as Sharded L7 VSs in Avi. Dedicated VSs will not be supported for Ingresses.
- Services of type:LoadBalancer will only be deployed as dedicated L4 virtual services in Avi
- Change of Sharding scheme requires a restart of AKO and will be service impacting
Document Revision History
|September 18, 2020||Published the Compatibility Guide for AKO version 1.2.1|
|July 20, 2020||Published the Compatibility Guide for AKO version 1.2.1 (Tech Preview)|