wodby cluster update-k3s-max-pods
Set how many pods each node of a k3s cluster runs at most
Set how many pods each node of a k3s cluster runs at most. k3s restarts on every node whose setting changes, one node at a time: apps keep running, the Kubernetes API pauses for about a minute while the server restarts, and new deployments wait until it ends. Refused while application operations are active, below the pods a node already runs, on a node with no free pod slot, and before the cluster's infrastructure upgrade that sets it.
Usage
wodby cluster update-k3s-max-pods CLUSTER_ID [flags]Options
| Flag | Description | Default |
|---|---|---|
--data string |
JSON request body | - |
-f, --file string |
Path to JSON request body | - |
-h, --help |
help for update-k3s-max-pods | false |
--max-pods int |
Pods each node runs at most, from 50 to 250 | 0 |
--timeout duration |
Maximum time to wait | 10m0s |
--wait |
Wait for the created task or deployment to finish | false |
Options inherited from parent commands
| Flag | Description | Default |
|---|---|---|
--access-token string |
Access token | - |
--api-base-url string |
Public REST API base URL | https://apiv2.wodby.com/v1 |
--api-key string |
API key | - |
--ci-config-path string |
Path to CI config | /tmp/.wodby-ci.json |
-o, --output string |
Output format: table, vertical, or json | table |
--verbose |
Verbose output | false |