Release Notes for
AKO
Version 1.13.1

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

What's New in
AKO
1.13.1

  • AKO
    now claims support for Kubernetes 1.31 and OCP 4.17.
  • AKO
    now supports multitenancy. For more information, see
    AKO
    Tenancy.
  • Support for EndpointSlices as the default mechanism for determining the network endpoints associated with a service in Kubernetes. For more information, see enableEndpointSlice in the
    Tunables for AKO
    topic.
  • Support for graceful shutdown of backend servers when EndpointSlices usage is enabled. For more information, see enableEndpointSlice in the
    Tunables for
    AKO
    topic.
  • Support for
    useRegex
    and
    applicationRootPath
    fields in HostRule CRD. For more information, see useRegex and applicationRootPath in the
    HostRule
    topic.
  • Support for
    enableHTTP2
    field in HTTPRule CRD. For more information, see enableHTTP2 in the
    HTTPRule
    topic.
  • Support for restricting cross-namespace usage of FQDNs/hostnames using the
    fqdnReusePolicy
    flag in ConfigMap. For more information, see FQDN Restriction.
  • AKO now supports OpenShift Routes with
    spec.subdomain
    field specified instead of
    spec.host
    field, using the
    defaultDomain
    field in
    ConfigMap
    . For more information, see NetworkSettings.defaultDomain in the
    Tunables for
    AKO
    topic.
AKO GatewayAPI implementation
  • Support for Service of type NodePortLocal.
  • Support for wildcard in
    Gateway
    listener
    Hostname
    .
  • Support for wildcard prefixed Hostname in HTTPRoute.
  • Support for ListenerConditionAccepted, ListenerConditionResolvedRefs and ListenerConditionProgrammed in Gateway Listener status, GatewayConditionAccepted and GatewayConditionProgrammed in Gateway status and RouteConditionAccepted and RouteConditionResolvedRefs in HTTPRoute status.
  • Support for sending 404 Response code, if no path matches for a request.
  • Support for multiple listeners in a Gateway having the same port and protocol and different hostname and name.
  • Support for graceful shutdown of backend servers.
  • Support for Endpointslices or Endpoints using
    enableEndpointSlice
    flag in configmap.
  • Events will now be raised if the status update of Gateway or HTTPRoute fails.

Issues Resolved in
AKO
1.13.1

  • AKO
    crashes when an Ingress is configured with a HostRule object that has the
    analyticsPolicy.logAllHeaders
    setting enabled.
  • AKO
    does not configure the
    Error Page Profile
    for an EVH parent shared virtual service when
    errorPageProfile
    is set in a matching HostRule object.
  • AKO
    -Gateway does not create a virtual service if Gateway has multiple listeners with the same hostname but a different port and a single HTTP route is attached to it.

Key Changes in
AKO
1.13.1

  • The
    L4Settings.defaultDomain
    field in Helm values.yaml is deprecated in favour of the newly introduced
    NetworkSettings.defaultDomain
    field. The value in the latter will be preferred for populating
    defaultDomain
    field in ConfigMap. For more information, see NetworkSettings.defaultDomain in the
    Tunables for
    AKO
    topic.
  • AKO
    now accepts Gateway with some valid and some invalid listeners.
  • AKO now allows the creation/updation of HTTPRoute and Gateway in any order. For more information, see Resource Creation in the
    Gateway API - v1
    topic.
  • HTTPRoute deletion will not update Gateway listener status with
    Virtual service deleted
    .
  • If the Secret specified in the TLS section does not exist,
    AKO
    will invalidate the Gateway listener and not generate any configuration corresponding to it. If an existing Secret is deleted, then Parent VS configurations corresponding to it will be deleted.

Known Issue in
AKO
1.13.1

  • If the tenant name contains invalid characters outside the range of (0-9/A-Z/a-z/-/_),
    AKO
    fails to create shared SNI parent VS VIPs.