Variable putNodeBalancerResponseSchemaConst
putNodeBalancerResponseSchema: ZodObject<
{
client_conn_throttle: ZodInt;
created: ZodReadonly<ZodISODateTime>;
hostname: ZodReadonly<ZodString>;
id: ZodReadonly<ZodInt>;
ipv4: ZodReadonly<ZodString>;
ipv6: ZodReadonly<ZodUnion<readonly [ZodReadonly<ZodString>, ZodNull]>>;
label: ZodString;
lke_cluster: ZodReadonly<
ZodUnion<
readonly [
ZodReadonly<
ZodObject<
{
id: ZodString;
label: ZodString;
type: ZodReadonly<ZodString>;
url: ZodString;
},
$strip,
>,
>,
ZodNull,
],
>,
>;
region: ZodReadonly<ZodString>;
tags: ZodArray<ZodString>;
transfer: ZodReadonly<
ZodObject<
{
in: ZodReadonly<
ZodUnion<readonly [ZodReadonly<ZodNumber>, ZodNull]>,
>;
out: ZodReadonly<ZodUnion<readonly [ZodReadonly<ZodNumber>, ZodNull]>>;
total: ZodReadonly<
ZodUnion<readonly [ZodReadonly<ZodNumber>, ZodNull]>,
>;
},
$strip,
>,
>;
type: ZodEnum<{ common: "common"; premium: "premium" }>;
updated: ZodReadonly<ZodISODateTime>;
},
$strip,
> = ...
NodeBalancer
Linode's load balancing solution. Can handle multiple ports, SSL termination, and any number of backends. NodeBalancer ports are configured with NodeBalancer configs, and each config is given one or more NodeBalancer nodes that accepts traffic. The traffic should be routed to the NodeBalancer's IP address, for the NodeBalancer to handle routing individual requests to backends.