You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lb-backend-create-usage.golden
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ ARGS:
14
14
[sticky-sessions-cookie-name] Cookie name for cookie-based sticky sessions
15
15
lb-id Load Balancer ID
16
16
[health-check.port] Port to use for the backend server health check
17
-
[health-check.check-delay] Time to wait between two consecutive health checks
18
-
[health-check.check-timeout] Maximum time a backend server has to reply to the health check
17
+
[health-check.check-delay=3s] Time to wait between two consecutive health checks
18
+
[health-check.check-timeout=1s] Maximum time a backend server has to reply to the health check
19
19
[health-check.check-max-retries] Number of consecutive unsuccessful health checks after which the server will be considered dead
20
20
[health-check.mysql-config.user] MySQL user to use for the health check
21
21
[health-check.pgsql-config.user] PostgreSQL user to use for the health check
@@ -37,9 +37,9 @@ ARGS:
37
37
[baremetal-server-id.{index}] UIID of the baremetal server.
38
38
[baremetal-server-tag.{index}] Tag of the baremetal server.
39
39
server-ip.{index} List of backend server IP addresses (IPv4 or IPv6) the backend should forward traffic to
40
-
[timeout-server] Maximum allowed time for a backend server to process a request
41
-
[timeout-connect] Maximum allowed time for establishing a connection to a backend server
42
-
[timeout-tunnel] Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout)
40
+
[timeout-server=5m] Maximum allowed time for a backend server to process a request
41
+
[timeout-connect=5s] Maximum allowed time for establishing a connection to a backend server
42
+
[timeout-tunnel=15m] Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout)
43
43
[on-marked-down-action] Action to take when a backend server is marked as down (on_marked_down_action_none | shutdown_sessions)
44
44
[proxy-protocol] Protocol to use between the Load Balancer and backend servers. Allows the backend servers to be informed of the client's real IP address. The PROXY protocol must be supported by the backend servers' software (proxy_protocol_unknown | proxy_protocol_none | proxy_protocol_v1 | proxy_protocol_v2 | proxy_protocol_v2_ssl | proxy_protocol_v2_ssl_cn)
45
45
[failover-host] Scaleway S3 bucket website to be served as failover if all backend servers are down, e.g. failover-website.s3-website.fr-par.scw.cloud
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lb-backend-update-usage.golden
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ ARGS:
13
13
forward-port-algorithm Load balancing algorithm to be used when determining which backend server to forward new traffic to (roundrobin | leastconn | first)
14
14
sticky-sessions Defines whether to activate sticky sessions (binding a particular session to a particular backend server) and the method to use if so. None disables sticky sessions. Cookie-based uses an HTTP cookie to stick a session to a backend server. Table-based uses the source (client) IP address to stick a session to a backend server (none | cookie | table)
15
15
[sticky-sessions-cookie-name] Cookie name for cookie-based sticky sessions
16
-
[timeout-server] Maximum allowed time for a backend server to process a request
17
-
[timeout-connect] Maximum allowed time for establishing a connection to a backend server
18
-
[timeout-tunnel] Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout)
16
+
[timeout-server=5m] Maximum allowed time for a backend server to process a request
17
+
[timeout-connect=5s] Maximum allowed time for establishing a connection to a backend server
18
+
[timeout-tunnel=15m] Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout)
19
19
[on-marked-down-action] Action to take when a backend server is marked as down (on_marked_down_action_none | shutdown_sessions)
20
20
[proxy-protocol] Protocol to use between the Load Balancer and backend servers. Allows the backend servers to be informed of the client's real IP address. The PROXY protocol must be supported by the backend servers' software (proxy_protocol_unknown | proxy_protocol_none | proxy_protocol_v1 | proxy_protocol_v2 | proxy_protocol_v2_ssl | proxy_protocol_v2_ssl_cn)
21
21
[failover-host] Scaleway S3 bucket website to be served as failover if all backend servers are down, e.g. failover-website.s3-website.fr-par.scw.cloud
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lb-frontend-create-usage.golden
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ARGS:
10
10
inbound-port Port the frontend should listen on
11
11
lb-id Load Balancer ID (ID of the Load Balancer to attach the frontend to)
12
12
backend-id Backend ID (ID of the backend the frontend should pass traffic to)
13
-
[timeout-client] Maximum allowed inactivity time on the client side
13
+
[timeout-client=5m] Maximum allowed inactivity time on the client side
14
14
[certificate-ids.{index}] List of SSL/TLS certificate IDs to bind to the frontend
15
15
[enable-http3] Defines whether to enable HTTP/3 protocol on the frontend
16
16
[zone=fr-par-1] Zone to target. If none is passed will use default zone from the config (fr-par-1 | fr-par-2 | nl-ams-1 | nl-ams-2 | pl-waw-1 | pl-waw-2)
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lb-frontend-update-usage.golden
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ARGS:
10
10
name Frontend name
11
11
inbound-port Port the frontend should listen on
12
12
backend-id Backend ID (ID of the backend the frontend should pass traffic to)
13
-
[timeout-client] Maximum allowed inactivity time on the client side
13
+
[timeout-client=5m] Maximum allowed inactivity time on the client side
14
14
[certificate-ids.{index}] List of SSL/TLS certificate IDs to bind to the frontend
15
15
[enable-http3] Defines whether to enable HTTP/3 protocol on the frontend
16
16
[zone=fr-par-1] Zone to target. If none is passed will use default zone from the config (fr-par-1 | fr-par-2 | nl-ams-1 | nl-ams-2 | pl-waw-1 | pl-waw-2)
| baremetal-server-tag.{index} || Tag of the baremetal server. |
311
311
| server-ip.{index} | Required | List of backend server IP addresses (IPv4 or IPv6) the backend should forward traffic to |
312
312
|~~send-proxy-v2~~| Deprecated | Deprecated in favor of proxy_protocol field |
313
-
| timeout-server || Maximum allowed time for a backend server to process a request |
314
-
| timeout-connect || Maximum allowed time for establishing a connection to a backend server |
315
-
| timeout-tunnel || Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout) |
313
+
| timeout-server |Default: `5m`| Maximum allowed time for a backend server to process a request |
314
+
| timeout-connect |Default: `5s`| Maximum allowed time for establishing a connection to a backend server |
315
+
| timeout-tunnel |Default: `15m`| Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout) |
316
316
| on-marked-down-action | One of: `on_marked_down_action_none`, `shutdown_sessions`| Action to take when a backend server is marked as down |
317
317
| proxy-protocol | One of: `proxy_protocol_unknown`, `proxy_protocol_none`, `proxy_protocol_v1`, `proxy_protocol_v2`, `proxy_protocol_v2_ssl`, `proxy_protocol_v2_ssl_cn`| Protocol to use between the Load Balancer and backend servers. Allows the backend servers to be informed of the client's real IP address. The PROXY protocol must be supported by the backend servers' software |
318
318
| failover-host || Scaleway S3 bucket website to be served as failover if all backend servers are down, e.g. failover-website.s3-website.fr-par.scw.cloud |
| sticky-sessions | Required<br />One of: `none`, `cookie`, `table`| Defines whether to activate sticky sessions (binding a particular session to a particular backend server) and the method to use if so. None disables sticky sessions. Cookie-based uses an HTTP cookie to stick a session to a backend server. Table-based uses the source (client) IP address to stick a session to a backend server |
482
482
| sticky-sessions-cookie-name || Cookie name for cookie-based sticky sessions |
483
483
|~~send-proxy-v2~~| Deprecated | Deprecated in favor of proxy_protocol field |
484
-
| timeout-server || Maximum allowed time for a backend server to process a request |
485
-
| timeout-connect || Maximum allowed time for establishing a connection to a backend server |
486
-
| timeout-tunnel || Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout) |
484
+
| timeout-server |Default: `5m`| Maximum allowed time for a backend server to process a request |
485
+
| timeout-connect |Default: `5s`| Maximum allowed time for establishing a connection to a backend server |
486
+
| timeout-tunnel |Default: `15m`| Maximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout) |
487
487
| on-marked-down-action | One of: `on_marked_down_action_none`, `shutdown_sessions`| Action to take when a backend server is marked as down |
488
488
| proxy-protocol | One of: `proxy_protocol_unknown`, `proxy_protocol_none`, `proxy_protocol_v1`, `proxy_protocol_v2`, `proxy_protocol_v2_ssl`, `proxy_protocol_v2_ssl_cn`| Protocol to use between the Load Balancer and backend servers. Allows the backend servers to be informed of the client's real IP address. The PROXY protocol must be supported by the backend servers' software |
489
489
| failover-host || Scaleway S3 bucket website to be served as failover if all backend servers are down, e.g. failover-website.s3-website.fr-par.scw.cloud |
0 commit comments