client/docs/cmd/kn_broker_update.md

51 lines
2.2 KiB
Markdown

## kn broker update
Update a broker
```
kn broker update NAME
```
### Examples
```
# Update a broker 'mybroker' in the current namespace with delivery sink svc1
kn broker update mybroker --dl-sink svc1
# Update a broker 'mybroker' in the 'myproject' namespace and with retry 2 seconds
kn broker update mybroker --namespace myproject --retry 2
```
### Options
```
--backoff-delay string The delay before retrying.
--backoff-policy string The retry backoff policy (linear, exponential).
--dl-sink string The sink receiving event that could not be sent to a destination.
-h, --help help for update
-n, --namespace string Specify the namespace to operate in.
--retry int32 The minimum number of retries the sender should attempt when sending an event before moving it to the dead letter sink.
--retry-after-max string An optional upper bound on the duration specified in a "Retry-After" header when calculating backoff times for retrying 429 and 503 response codes. Setting the value to zero ("PT0S") can be used to opt-out of respecting "Retry-After" header values altogether. This value only takes effect if "Retry" is configured, and also depends on specific implementations (Channels, Sources, etc.) choosing to provide this capability.
--timeout string The timeout of each single request. The value must be greater than 0.
```
### Options inherited from parent commands
```
--as string username to impersonate for the operation
--as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups
--as-uid string uid to impersonate for the operation
--cluster string name of the kubeconfig cluster to use
--config string kn configuration file (default: ~/.config/kn/config.yaml)
--context string name of the kubeconfig context to use
--kubeconfig string kubectl configuration file (default: ~/.kube/config)
--log-http log http traffic
```
### SEE ALSO
* [kn broker](kn_broker.md) - Manage message brokers