New GatewayClassConditionReason: ParametersRequired

[aharbis]

The GatewayClass API reference states the following for parametersRef:

ParametersRef is a reference to a resource that contains the configuration parameters corresponding to the GatewayClass. This is optional if the controller does not require any additional configuration.

However, it's not made clear what the behavior should be for a Gateway implementation which requires this additional configuration. Looking at GatewayClassConditionReason, the closest is InvalidParameters but this doesn't seem quite right for this use case.

I'd like to propose a new reason type, ParametersRequired, to provide a clear reason for rejecting a GatewayClass which does not specify parametersRef for Gateway implementations which require it.

[howardjohn]

IMO InvalidParameters should just be expanded to support this. The parameters are invalid -- its an implementation-specific reason why they are invalid (they are required for your use case) but in the end its invalid. I don't think we want tons of reasons, the details can be explained in message

[mikemorris]

Agreed, and we could do a minor docs update if needed to explicitly expand the scope for this reason.