RateLimitPolicy add Gateway API policy attachment (target ref)

[maleck13]

To bring the Rate Limit Policy API in line with the policy attachment concept from Gateway API, we need to add a target ref We also need to consider support default and override along with the inheritance model.

// PolicyTargetReference identifies an API object to apply policy to.
type PolicyTargetReference struct {
    // Group is the group of the target resource.
    //
    // +kubebuilder:validation:MinLength=1
    // +kubebuilder:validation:MaxLength=253
    Group string `json:"group"`

    // Kind is kind of the target resource.
    //
    // +kubebuilder:validation:MinLength=1
    // +kubebuilder:validation:MaxLength=253
    Kind string `json:"kind"`

    // Name is the name of the target resource.
    //
    // +kubebuilder:validation:MinLength=1
    // +kubebuilder:validation:MaxLength=253
    Name string `json:"name"`

    // Namespace is the namespace of the referent. When unspecified, the local
    // namespace is inferred. Even when policy targets a resource in a different
    // namespace, it may only apply to traffic originating from the same
    // namespace as the policy.
    //
    // +kubebuilder:validation:MinLength=1
    // +kubebuilder:validation:MaxLength=253
    // +optional
    Namespace string `json:"namespace,omitempty"`
}

• Support targeting a HTTPRoute with the target ref #123
• [Investigation] RLP defaults and how we would apply them #124
• [Investigation] RLP can target a Gateway resource #129
• Document the RateLimitPolicy design and backing WASM design #131
• New RateLimitPolicy demo for showing Gateway support #132
• Document with examples the behaviour of RLP #172
• Optional [Investigation] Supporting Overrides in RateLimitPolicy #122
• Implement targeting Gateway API Gateway #160
• RLP status with gateway configuration #204

[maleck13]

Initially we may want to skip the Namespace option here as I don't think it is relevant

[rahulanand16nov]

It's recommended in the doc to use the same structs so, even if Namespace is present, we can ignore its usage in the controller.

[maleck13]

👍

[maleck13]

Lets target the Gateway API HTTPRoute first

[eguzki]

Added Support targeting a TLSRoute with the target ref task to the epic