rpk cluster quotas alter
Add or delete a client quota.
A client quota consists of an entity (to which the quota is applied) and a quota type (what is being applied).
There are two entity types supported by Redpanda: client ID and client ID prefix. Use the --default flag to assign quotas to default entity types.
You can perform a dry run using the --dry flag.
Flags
| Value | Type | Description |
|---|---|---|
|
strings |
Key=value quota to add, where the value is a float number (repeatable). |
|
strings |
Entity type for default matching, where type is client-id or client-id-prefix (repeatable). |
|
strings |
Key of the quota to delete (repeatable). |
|
- |
Perform a dry run. Validate the request without altering the quotas. Show what would be done, but do not execute the command. |
|
string |
Output format. Possible values: |
|
- |
Help for alter. |
|
strings |
Entity for exact matching. Format |
|
string |
Redpanda or |
|
stringArray |
Override |
|
string |
Profile to use. See |
|
- |
Enable verbose logging. |
Examples
Add quota (consumer_byte_rate) to client ID <foo>:
rpk cluster quotas alter --add consumer_byte_rate=200000 --name client-id=<foo>
Add quota (consumer_byte_rate) to client ID starting with <bar>-:
rpk cluster quotas alter --add consumer_byte_rate=200000 --name client-id-prefix=<bar>-
Add quota (producer_byte_rate) to default client ID:
rpk cluster quotas alter --add producer_byte_rate=180000 --default client-id
Remove quota (producer_byte_rate) from client ID foo:
rpk cluster quotas alter --delete producer_byte_rate --name client-id=<foo>