AKO

now claims support for Kubernetes 1.29, OCP version 4.14.

AKO

supports

LoadBalancerClass

for

LoadBalancer

type services.

AKO

allows pool member to be IPv6 or IPv4 in dual stack deployment for CALICO and ANTREA CNI.

IPv6 address can be used to connect to the

Avi Load Balancer Controller

.

VRF support within VCenter Cloud.

AKO

now has a L7Rule CRD to change default parameters of L7 VirtualService in addition to HostRule CRD.

Support for Network Security policy in HostRule CRD.

AKO

can use pre-existing

avi-secret

present in

AKO

helm installation namespace to connect to the

Avi Load Balancer Controller

. Do not specify credentials as part of values.yaml during installation.

AKO

allows VIP to be IPV6 for

LoadBalancer

type services.

Static routes are not added due to an error: Field check for static_routes failed: Unique constraints

route_id

has duplicated value when calico CNI allocates multiple block-affinities for a node and that may result in

AKO

crash.

Failure in creating virtual service, pool group and other pools if the name of one of the pool attached to the pool group, exceeds the maximum

Avi Load Balancer Controller

name length limit.

L4 CRD can be applied to

LoadBalancer

type service present in different namespace.

AKO

shows all IPV4 and IPV6 addresses associated with

VirtualService

as part of Ingress, LoadBalancer status.

AKO

updates Route's Status:

Reason field with vsuuid and controller uuid

.

L4 Rule CRD, with

enableSSL: true

in listener properties, will not be applied to L4 Virtual Service if the

Avi Load Balancer Controller

license is of type Enterprise with Cloud Service.