InlineLBVirtualServer1
{
"access_log_enabled": false,
"application_profile_path": "string",
"client_ssl_profile_binding": {
"certificate_chain_depth": 0,
"client_auth": "string",
"client_auth_ca_paths": [
"string"
],
"client_auth_crl_paths": [
"string"
],
"default_certificate_path": "string",
"sni_certificate_paths": [
"string"
],
"ssl_profile_path": "string"
},
"default_pool_member_ports": [
"string"
],
"enabled": false,
"ip_address": "string",
"lb_persistence_profile_path": "string",
"lb_service_path": "string",
"max_concurrent_connections": 0,
"max_new_connection_rate": 0,
"pool_path": "string",
"ports": [
"string"
],
"rules": [
{
"actions": [
{
"type": "string"
}
],
"display_name": "string",
"match_conditions": [
{
"inverse": false,
"type": "string"
}
],
"match_strategy": "string",
"phase": "string"
}
],
"server_ssl_profile_binding": {
"certificate_chain_depth": 0,
"client_certificate_path": "string",
"server_auth": "string",
"server_auth_ca_paths": [
"string"
],
"server_auth_crl_paths": [
"string"
],
"ssl_profile_path": "string"
},
"sorry_pool_path": "string"
}If access log is enabled, all HTTP requests sent to an L7 virtual server are logged to the access log file. Both successful requests (backend server returns 2xx) and unsuccessful requests (backend server returns 4xx or 5xx) are logged to access log, if enabled.
The application profile defines the application protocol characteristics. It is used to influence how load balancing is performed. Currently, LBFastTCPProfile, LBFastUDPProfile and LBHttpProfile, etc are supported.
Default pool member ports when member port is not defined.
Flag to enable the load balancer virtual server.
Configures the IP address of the LBVirtualServer where it receives all client connections and distributes them among the backend servers.
Path to optional object that enables persistence on a virtual server allowing related client connections to be sent to the same backend server. Persistence is disabled by default.
virtual servers can be associated to LBService(which is similar to physical/virtual load balancer), LB virtual servers, pools and other entities could be defined independently, the LBService identifier list here would be used to maintain the relationship of LBService and other LB entities.
To ensure one virtual server does not over consume resources, affecting other applications hosted on the same LBS, connections to a virtual server can be capped. If it is not specified, it means that connections are unlimited.
To ensure one virtual server does not over consume resources, connections to a member can be rate limited. If it is not specified, it means that connection rate is unlimited.
The server pool(LBPool) contains backend servers. Server pool consists of one or more servers, also referred to as pool members, that are similarly configured and are running the same application.
Ports contains a list of at least one port or port range such as "80", "1234-1236". Each port element in the list should be a single port or a single port range.
Load balancer rules allow customization of load balancing behavior using match/action rules. Currently, load balancer rules are supported for only layer 7 virtual servers with LBHttpProfile.
When load balancer can not select a backend server to serve the request in default pool or pool in rules, the request would be served by sorry server pool.