mirror of
https://github.com/kubernetes/node-problem-detector.git
synced 2026-02-14 18:09:57 +00:00
chore: fix misspelling
This commit is contained in:
@@ -1,9 +1,11 @@
|
||||
# Custom Plugin Monitor
|
||||
|
||||
## Configuration
|
||||
|
||||
### Plugin Config
|
||||
|
||||
* `invoke_interval`: Interval at which custom plugins will be invoked.
|
||||
* `timeout`: Time after which custom plugins invokation will be terminated and considered timeout.
|
||||
* `timeout`: Time after which custom plugins invocation will be terminated and considered timeout.
|
||||
* `max_output_length`: The maximum standard output size from custom plugins that NPD will be cut and use for condition status message.
|
||||
* `concurrency`: The plugin worker number, i.e., how many custom plugins will be invoked concurrently.
|
||||
* `enable_message_change_based_condition_update`: Flag controls whether message change should result in a condition update.
|
||||
|
||||
@@ -14,11 +14,11 @@ itself.
|
||||
viewing the changes on GitHub ([example:
|
||||
https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master](https://github.com/kubernetes/node-problem-detector/compare/v0.8.6...master)).
|
||||
|
||||
1. Based on the changes to be included in the release, determine what the next
|
||||
2. Based on the changes to be included in the release, determine what the next
|
||||
release number should be. We strive to follow [SemVer](https://semver.org/)
|
||||
as much as possible.
|
||||
|
||||
1. Update [CHANGELOG](https://github.com/kubernetes/node-problem-detector/blob/master/CHANGELOG.md)
|
||||
3. Update [CHANGELOG](https://github.com/kubernetes/node-problem-detector/blob/master/CHANGELOG.md)
|
||||
with all significant changes.
|
||||
|
||||
## Create release
|
||||
@@ -31,11 +31,11 @@ body of the release:
|
||||
release (e.g.
|
||||
[https://github.com/kubernetes/node-problem-detector/compare/v0.8.5...v0.8.6](https://github.com/kubernetes/node-problem-detector/compare/v0.8.5...v0.8.6)).
|
||||
|
||||
1. There is no need to duplicate everything from the CHANGELOG, but include the
|
||||
2. There is no need to duplicate everything from the CHANGELOG, but include the
|
||||
most significant things so someone just viewing the release entry will have
|
||||
an idea of what it includes.
|
||||
|
||||
1. Provide a link to the new image release (e.g. `Image:
|
||||
3. Provide a link to the new image release (e.g. `Image:
|
||||
k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.6`)
|
||||
|
||||
## Post release steps
|
||||
|
||||
Reference in New Issue
Block a user