mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2024-12-14 11:57:51 +00:00
25e827a4c8
The feature gate is locked to true. That is, it is not possible to revert back to the gPRC-based communication which makes the gRPC API ready for removal.
29 lines
970 B
Markdown
29 lines
970 B
Markdown
---
|
|
title: "NFD-Garbage-Collector"
|
|
layout: default
|
|
sort: 6
|
|
---
|
|
|
|
# NFD-GC
|
|
{: .no_toc}
|
|
|
|
---
|
|
|
|
NFD-GC (NFD Garbage-Collector) is preferably run as a Kubernetes deployment
|
|
with one replica. It makes sure that all
|
|
[NodeFeature](custom-resources.md#nodefeature) and
|
|
[NodeResourceTopology](custom-resources.md#noderesourcetopology) objects
|
|
have corresponding nodes and removes stale objects for non-existent nodes.
|
|
|
|
The daemon watches for Node deletion events and removes NodeFeature and
|
|
NodeResourceTopology objects upon them. It also runs periodically to make sure
|
|
no node delete event was missed and to remove any NodeFeature or
|
|
NodeResourceTopology objects that were created without corresponding node. The
|
|
default garbage collector interval is set to 1h which is the value when no
|
|
-gc-interval is specified.
|
|
|
|
## Configuration
|
|
|
|
In Helm deployments see
|
|
[garbage collector parameters](../deployment/helm.md#garbage-collector-parameters)
|
|
for altering the nfd-gc configuration.
|