Limits of fields in KongConsumer and KongConsumerGroup

[randmonkey]

Current Behavior

Limits of Consumers in Konnect:

• username's length < 128 and match regex ^[\p{L}\p{N}.\-_~+@/\[\]]+(?: [\p{L}\p{N}.\-_~+@/\[\]]+)*$
• custom_id match regex ^[0-9a-zA-Z.\-_~\(\)#%@|+\[\]]+(?: [0-9a-zA-Z.\-_~\\(\)#%@|+\\[\\]]+)*$
  Limits of consumer groups in Konnect:
• name's length < 128 and match regex ^[\p{N}\p{L}.\-_~]*$

Currently they are not validated on CRD layer or controller layer, and invalid KongConsumer or KongConsumerGroup will be sent to Konnect and get 400 responses. Controller keeps retry in such cases.

Expected Behavior

Either:

• Validate and reject invalid instances of KongConsumers and KongConsumerGroups
• Or detect the validation errors and stop reconciliations of invalid resources

Steps To Reproduce

Operator Version

kubectl version

[pmalek]

... invalid KongConsumer or KongConsumerGroup will be sent to Konnect and get 400 responses. Controller keeps retry in such cases.

With recent introduction of

gateway-operator/controller/konnect/ops/ops.go

Line 382 in 73b907c

return ctrl.Result{}, IgnoreUnrecoverableAPIErr(err, loggerForEntity(ctx, e, UpdateOp))

and

gateway-operator/controller/konnect/ops/ops.go

Line 177 in 73b907c

return e, IgnoreUnrecoverableAPIErr(err, loggerForEntity(ctx, e, CreateOp))

those should be ignored (i.e. the error shouldn't be reported from the reconcile loop and thus this should not be retried).