This is based on the feedback here: #13014 (comment)

Currently remote jwks source url is constructed using k8s svc/static backend configuration, tls settings from an AgentgatewayBackend/AgentgatewayPolicy, and contents of the jwksPath field of the AgentgatewayPolicy. This is quite verbose if no changes to tls configuration are required or plain-text http is used. For such cases a text field containing a complete url to a remote jwks source could be a concise alternative.

Notes

Introducing a text field in remote jwks api would result in inconsistent api, as we don't use this approach in other similar cases (e.g. when defining "normal" agw backends). To keep api consistent we should also consider similar change for other types of backends too.

Potential approach could be to support either text field, or require a combination of path and backendRef to be present. In this case url and current jwksPath fields would be separate fields.