Problem Statement

The fact that GatewayConfiguration has to be done at the GatewayClass level is frictional. On one hand it means we have to create a separate GatewayClass for any Gateways we want to have a unique configuration, which is bad user experience. On the other hand for bespoke setups like AIGateway this forces the user to have to provide a GatewayConfiguration for any changes they need and doesn't allow the AIGateway controller to manage this, as it would not be reasonable for the AIGateway controller to update its own GatewayClass.

Proposed Solution

Make it possible to apply GatewayConfigurations at the individual Gateway level.

Additional Information

Ideally we would work with upstream on this to come up with a standard mechanism.

Acceptance Criteria

• users or integrations can create GatewayConfiguration resources that are associated with an individual Gateway using the parametersRef of GatewayInfrastructure