mirrors/node-feature-discovery
mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-05 08:17:04 +00:00
Code Activity

docs: drop "currently"

Browse source 
All the documentation describes the current version of NFD (it not
stated otherwise).
This commit is contained in:
Markus Lehtonen 2023-12-01 15:43:00 +02:00
parent 2f3cfbf209
commit da64884d02
4 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/deployment/image-variants.md
View file

@ -9,8 +9,8 @@ sort: 1
---
NFD currently offers two variants of the container image. The "minimal" variant is
currently deployed by default. Released container images are available for
NFD offers two variants of the container image. The "minimal" variant is
deployed by default. Released container images are available for
x86_64 and Arm64 architectures.
## Minimal

2
docs/developer-guide/index.md
View file

@ -125,7 +125,7 @@ makefile overrides.
| KUBECONFIG | Kubeconfig for running e2e-tests | *empty* |
| E2E_TEST_CONFIG | Parameterization file of e2e-tests (see [example][e2e-config-sample]) | *empty* |
| E2E_PULL_IF_NOT_PRESENT | True-ish value makes the image pull policy IfNotPresent (to be used only in e2e tests) | false |
| OPENSHIFT | Non-empty value enables OpenShift specific support (currently only effective in e2e tests) | *empty* |
| OPENSHIFT | Non-empty value enables OpenShift specific support (only affects e2e tests) | *empty* |
For example, to use a custom registry:

2
docs/reference/master-configuration-reference.md
View file

@ -78,7 +78,7 @@ default `feature.node.kubernetes.io/` prefix to unprefixed labels, annotations
and extended resources - this is also the default behavior in NFD v0.13 and
earlier. When the option is set to `false`, no prefix will be prepended to
unprefixed names, effectively causing them to be filtered out (as NFD does not
currently allow unprefixed names of labels, annotations or extended resources).
allow unprefixed names of labels, annotations or extended resources).
The default will be changed to `false` in a future release.
For example, with the `autoDefaultNs` set to `true`, a NodeFeatureRule with

3
docs/usage/nfd-topology-updater.md
View file

@ -62,8 +62,7 @@ NFD-Topology-Updater supports configuration through a configuration file. The
default location is `/etc/kubernetes/node-feature-discovery/topology-updater.conf`,
but, this can be changed by specifying the`-config` command line flag.
> **NOTE:** unlike nfd-worker, dynamic configuration updates are not currently
> supported.
> **NOTE:** unlike nfd-worker, dynamic configuration updates are not supported.
Topology-Updater configuration file is read inside the container,
and thus, Volumes and VolumeMounts are needed