Release Notes for
AKO
Version 1.11.1

This section lists the new features, issues resolved and known issues in
AKO
version 1.11.1.

What’s New in
AKO
Version 1.11.1

  • Support for gateway API (Tech Preview).
  • Support for configuring the nsxt1lr in AviInfrasetting.
  • SSL support for L4 virtual services with L4Rule CRD.
  • AKO
    supports
    image pull secret
    to pull
    AKO
    image from secured registries.

Issues Resolved in
AKO
Version 1.11.1

  • AKO
    programs routes with secondary IPs in OpenShift.
  • When
    HTTPRules
    are applied to the ingresses, with same FQDN and path but deployed in different namespaces, then
    httprule
    config is removed from one of the pool when another
    httprule
    is applied.
  • Virtual service and pools are not deleted when multiple ingress use same infrasetting for shard size.
  • DNS mentioned in
    external-dns.alpha.kubernetes.io/hostname
    is not added as part
    host-fqdn-vs-uuid-map
    or vsvip dns info
    if ako.vmware.com/enable-shared-vip
    annotation is also applied to the LB service.
  • Ports 80 and 443 are associated with Dedicated Insecure virtual services by default when no listeners are defined in
    HostRule
    CRD.
  • If only
    loadBalancerIP
    is provided and no listeners are specified in the
    HostRuletcpSettings
    section, the virtual services creation fails with error:
    Service mandatory for Virtual Service
    .

Key Changes in
AKO
Version 1.11.1

  • API version for AviInfrasetting, Hostrule and HTTPRule has been updated from
    v1alpha1
    to
    v1beta1
    . Update CRD definitions before upgrading
    AKO
    to 1.11.1.
  • Add Hostname from external-dns annotation only when AutoFQDN is flat or default for service type LB.
  • Reduce the length of the label created by the
    AKO
    when the AutoFQDN is set as flat for service of Type LB.
  • Do not add gslbFqdn, mentioned in Hostrule, to the vsvip fqdn when
    AKO
    is running in Dedicated mode.

Known Issue in
AKO
Version 1.11.1

  • For
    Avi Load Balancer
    version less than 30.1.1, when using
    SSORule
    CRD, if
    authnReqAcsType
    is set to
    SAML_AUTHN_REQ_ACS_TYPE_URL
    , Request Body Buffering needs to be enabled for EVH parent virtual service for SAML traffic to work. This can be achieved by creating a custom application profile of type HTTP in the
    Avi Load Balancer
    with Request Body Buffering enabled and attaching that application profile to the EVH parent VS by using a HostRule CRD object. The
    Avi Load Balancer
    version 30.1.1 is supported starting with
    AKO
    version 1.11.1.