Endpoints, authentication and the connection settings both sides share.
Each URL may be an origin, a reverse-proxy base path, or an existing
/write/v4 or /read/v1 endpoint; each side derives its own route.
OptionalegressThe query sessions' options, on the same terms as ingress.
OptionalingressThe pooled senders' options. url, failoverUrls and authorization
belong to cluster; any other connection setting given here overrides
the cluster's for ingress only.
OptionallazyCoordinates a non-blocking startup: ingress connects in the background,
using memory replay when store-and-forward is absent, and the egress pool
remains cold until the first query. Conflicts with a positive queryPoolMin,
an ingress initialConnectMode other than async, or ingress
reconnect: false. This is the typed spelling of the lazy_connect key,
which, as in the Java, Rust and Python clients, only the pooled client
applies.
Optionalpool
Node configuration for a combined pooled QWP ingress/egress client. One endpoint list and authentication are shared, while side-specific options remain explicit.