Use the

fqdnReusePolicy

knob in the

L7Settings

section of values.yaml to restrict FQDN to a single namespace:

L7Settings:
   .
   .
   .
   fqdnReusePolicy: "InterNamespaceAllowed"

The

fqdnReusePolicy

knob can be set to either

InterNamespaceAllowed

or

Strict

values. When the value is

InterNamespaceAllowed

,

AKO

accepts ingresses with the same host/FQDN from all namespaces. By default, the value is set to

InterNamespaceAllowed

.

When the value is

Strict

,

AKO

restricts the FQDN to a single namespace. The FQDN will be associated with the namespace that claims it first. For example, if ingress1 in the red namespace is deployed with

foo.avi.internal

, then with the Strict setting,

foo.avi.internal

will be associated with the red namespace. If ingress2 in the default namespace is deployed using the same FQDN (

foo.avi.internal

),

AKO

will reject ingress2 with the message

host already claimed

, and the virtual service and related

Avi Load Balancer Controller

objects for ingress2 will not be created.

In the

Strict

setting,

AKO

does not automatically associate one FQDN with another namespace even if all ingresses using that FQDN are deleted from the originally claimed namespace. For example, if ingress1 in the red namespace is deleted and no other ingress in the red namespace is associated with

foo.avi.internal

,

AKO

will not automatically associate

foo.avi.internal

with ingress2 in the default namespace. The user must perform a create or update operation on the ingresses associated with

foo.avi.internal

to claim the FQDN. Alternatively, the user can reboot

AKO

to associate

foo.avi.internal

with the default namespace.

For ingresses with multiple hosts (FQDNs), if any one of the FQDNs is not accepted by

AKO

, the entire ingress will be rejected, and the configuration defined within that ingress will not be applied to the

Avi Load Balancer Controller

.

AKO

has similar behaviour for OpenShift Routes under this knob.