Application Gateway for Containers API specification for Kubernetes

"application-cookie"

AffinityTypeApplicationCookie is a session affinity type for an application cookie

"managed-cookie"

AffinityTypeManagedCookie is a session affinity type for a managed cookie

"Accepted"

AlbReasonAccepted indicates that the Application Gateway for Containers resource are accepted by the controller.

"Ready"

AlbReasonDeploymentReady indicates the Application Gateway for Containers resource deployment status.

"InProgress"

AlbReasonInProgress indicates whether the Application Gateway for Containers resource is in the process of being created, updated, or deleted.

"Accepted"

AlbConditionTypeAccepted indicates whether the Application Gateway for Containers resource are accepted by the controller.

"Deployment"

AlbConditionTypeDeployment indicates the deployment status of the Application Gateway for Containers resource.

Associations are subnet resource IDs the Application Gateway for Containers resource are associated with.

Known condition types are:

• “Accepted”
• “Ready”

Object’s metadata.

Spec is the specifications for Application Gateway for Containers resource.

Status defines the current state of Application Gateway for Containers resource.

Object’s metadata.

Spec is the BackendLoadBalancingPolicy specification.

Status defines the current state of BackendLoadBalancingPolicy.

"Accepted"

BackendLoadBalancingPolicyReasonAccepted is used to set the BackendLoadBalancingPolicyConditionReason to Accepted When the given BackendLoadBalancingPolicy is correctly configured

"Conflicted"

BackendLoadBalancingPolicyReasonConflicted is used when the target ref conflicts with a pre-existing policy target

"InvalidBackendLoadBalancingPolicy"

BackendLoadBalancingPolicyReasonInvalid is the reason when the BackendLoadBalancingPolicy isn’t Accepted

"InvalidGroup"

BackendLoadBalancingPolicyReasonInvalidGroup is used when the group is invalid

"InvalidKind"

BackendLoadBalancingPolicyReasonInvalidKind is used when the kind/group is invalid

"InvalidName"

BackendLoadBalancingPolicyReasonInvalidName is used when the name is invalid

"InvalidService"

BackendLoadBalancingPolicyReasonInvalidService is used when the Service is invalid

"NoTargetReference"

BackendLoadBalancingPolicyReasonNoTargetReference is used when there’s no target reference

"RefNotPermitted"

BackendLoadBalancingPolicyReasonRefNotPermitted is used when the ref isn’t permitted

"ResolvedRefs"

BackendLoadBalancingPolicyReasonResolvedRefs is used to set the BackendLoadBalancingPolicyConditionReason to ResolvedRefs when the given BackendLoadBalancingPolicy has correct references

"Accepted"

BackendLoadBalancingPolicyConditionAccepted is used to set the BackendLoadBalancingPolicyConditionType to Accepted

"ResolvedRefs"

BackendLoadBalancingPolicyConditionResolvedRefs is used to set the BackendLoadBalancingPolicyCondition to ResolvedRefs

Port is the port to use for connection to the backend

TargetRefs identifies a list of API objects to apply policy to.

LoadBalancing defines the schema for configuring Load Balancing options

Object’s metadata.

Spec is the BackendTLSPolicy specification.

Status defines the current state of BackendTLSPolicy.

(Members of CommonTLSPolicy are embedded into this type.)

Sni is the server name to use for the TLS connection to the backend.

Ports specifies the list of ports where the policy is applied.

ClientCertificateRef is the reference to the client certificate to use for the TLS connection to the backend.

Port is the port to use for the TLS connection to the backend

TargetRef identifies an API object to apply policy to.

Override defines policy configuration that should override policy configuration attached below the targeted resource in the hierarchy.

Note: Override is currently not supported and result in a validation error. Support for Override will be added in a future release.

Default defines default policy configuration for the targeted resource.

Conditions describe the current conditions of the BackendTLSPolicy.

Implementations should prefer to express BackendTLSPolicy conditions using the BackendTLSPolicyConditionType and BackendTLSPolicyConditionReason constants so that operators and tools can converge on a common vocabulary to describe BackendTLSPolicy state.

Known condition types are:

• “Accepted”
• “ResolvedRefs”

Verify provides the options to verify the peer certificate.

CaCertificateRef is the CA certificate used to verify peer certificate.

SubjectAltName is the subject alternative name used to verify peer certificate.

(Members of NamespacedPolicyTargetReference are embedded into this type.)

SectionNames is the name of the section within the target resource. When unspecified, this targetRef targets the entire resource. In the following resources, SectionNames is interpreted as the following:

• Gateway: Listener Name
• Service: Port Name

If a SectionNames is specified, but doesn’t exist on the targeted object, the Policy fails to attach, and the policy implementation will record a ResolvedRefs or similar Condition in the Policy’s status.

Object’s metadata.

Spec is the FrontendTLSPolicy specification.

Status defines the current state of FrontendTLSPolicy.

Verify provides the options to verify the peer certificate.

Type is the type of the policy.

TargetRef identifies an API object to apply policy to.

Default defines default policy configuration for the targeted resource.

Override defines policy configuration that should override policy configuration attached below the targeted resource in the hierarchy.

Note: Override is currently not supported and result in a validation error. Support for Override will be added in a future release.

Conditions describe the current conditions of the FrontendTLSPolicy.

Implementations should prefer to express FrontendTLSPolicy conditions using the FrontendTLSPolicyConditionType and FrontendTLSPolicyConditionReason constants so that operators and tools can converge on a common vocabulary to describe FrontendTLSPolicy state.

Known condition types are:

• “Accepted”

"predefined"

PredefinedFrontendTLSPolicyType is the type of the predefined Frontend TLS Policy.

"2023-06"

PredefinedPolicy202306 is the name of the predefined Frontend TLS Policy for the policy “2023-06”.

"2023-06-S"

PredefinedPolicy202306Strict is the name of the predefined Frontend TLS Policy for the policy “2023-06-S”. This is a strict version of the policy “2023-06”.

Authority if present is used as the value of the Authority header in the health check.

Service allows the configuration of a Health check registered under a different service name.

Name is the name of the HTTP Header to be matched. Name matching MUST be case insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).

If multiple entries specify equivalent header names, the first entry with an equivalent name MUST be considered for a match. Subsequent entries with an equivalent header name MUST be ignored. Due to the case-insensitivity of header names, “foo” and “Foo” are considered equivalent.

Value is the value of HTTP Header to be matched.

Body defines the HTTP body matchers to use for HealthCheck checks.

StatusCodes defines the HTTP status code matchers to use for HealthCheck checks.

Type defines the type of path modifier. More types may be added in a future release of the API.

Values may be added to this enum, implementations must ensure unknown values won’t cause a crash.

Unknown values here must result in the implementation setting the Accepted Condition for the rule to be false

ReplaceFullPath specifies the value with which to replace the full path of a request during a rewrite or redirect.

ReplacePrefixMatch specifies the value with which to replace the prefix match of a request during a rewrite or redirect. For example, a request to “/foo/bar” with a prefix match of “/foo” and a ReplacePrefixMatch of “/xyz” would be modified to “/xyz/bar”.

This matches the behavior of the PathPrefix match type. This matches full path elements. A path element refers to the list of labels in the path split by the / separator. When specified, a trailing / is ignored. For example, the paths /abc, /abc/, and /abc/def would all match the prefix /abc, but the path /abcd wouldn’t.

ReplacePrefixMatch is only compatible with a PathPrefix HTTPRouteMatch. Using any other HTTPRouteMatch type on the same HTTPRouteRule results in the implementation setting the Accepted Condition for the Route to status: False.