mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-04-07 01:24:33 +00:00
add documentation
This commit is contained in:
parent
5162c2ebe5
commit
3f941a760c
2 changed files with 12 additions and 0 deletions
docs
|
@ -31,6 +31,11 @@ Print usage and exit.
|
|||
|
||||
Print version and exit.
|
||||
|
||||
### -list-size
|
||||
|
||||
The pagination size to use when calling api-server to list nodefeatures.
|
||||
Pagination is useful for controlling the load on api-server/etcd as the nodefeature resources can be large.
|
||||
|
||||
### -gc-interval
|
||||
|
||||
The `-gc-interval` specifies the interval between periodic garbage collector runs.
|
||||
|
|
|
@ -27,3 +27,10 @@ default garbage collector interval is set to 1h which is the value when no
|
|||
In Helm deployments see
|
||||
[garbage collector parameters](../deployment/helm.md#garbage-collector-parameters)
|
||||
for altering the nfd-gc configuration.
|
||||
|
||||
## List Pagination & Scalability
|
||||
|
||||
When NFD GC runs up it lists nodefeatures from api-server.
|
||||
These resources can be large and in a large cluster this initial list call to sync the informer cache can be
|
||||
expensive and heavy on api-server/etcd. You can use the `list-size` argument to control pagination size
|
||||
to help control the load from this list.
|
||||
|
|
Loading…
Add table
Reference in a new issue