Avi Multi-Cluster Kubernetes Operator Version 1.4 Release Notes
The Avi Vantage platform integration with OpenShift/ Kubernetes an operator called Avi Multi-Cluster Kubernetes Operator (AMKO) to facilitate multi-cluster application deployments. The following illustration outlines the components of the Avi Kubernetes integration.
What’s New in AMKO Version 1.4.2
Support for Federation (to be enabled during Installation).
A new custom resource AMKOCluster for federation configuration.
AMKO can now boot up, even if one of the member clusters is unreachable. If the cluster is available later on, AMKO will start it’s informers.
Issues Resolved in AMKO Version 1.4.2
- Parsing error for TTL and hash mask fields after creation of GslbServices
- Path based health monitors get unnecessarily created and then deleted sometimes, even if custom health monitor refs are provided
- GslbServices unnecessarily updated due to incorrect parsing of site persistence field
- AMKO does not
panicif the GSLB leader details could not be fetched.
What’s New in AMKO Version 1.4.1
Support for GslbService properties: TTL, Site Persistence and Custom Health Monitors via GlobalDeploymentPolicy and GSLBHostRule
Support for pool algorithm settings in
Support for adding third party site members via GSLBHostRule
Key Changes in AMKO 1.4.1
- GDP version change from v1alpha1 to v1alpha2
End of Support
- GDP version v1alpha1 is not supported with AMKO 1.4.1
Known Issues in AMKO 1.4.1
HTTP Health Monitors are not supported for GslbServices with secure objects as pool members (with AKO 1.4.1)
Site-persistence is not supported for insecure ingress.
To install AMKO and get started, refer to the AMKO Installation Guide.
For more information about AMKO, refer to the Documentation for AMKO.
To know more about comp matrix for AMKO across various parameters, refer to the Compatibility Guide for AMKO.
Document Revision History
|May 5, 2021||Published the Release Notes for AMKO version 1.4.1|