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 16:27:05 +00:00
Code Activity

docs: don't use "we"

Browse source
This commit is contained in:
Markus Lehtonen 2023-12-01 15:39:16 +02:00
parent fea395d005
commit 2f3cfbf209
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/deployment/helm.md
View file

@ -86,8 +86,8 @@ deletes the release.
## Chart parameters ## Chart parameters
In order to tailor the deployment of the Node Feature Discovery to your cluster needs To tailor the deployment of the Node Feature Discovery to your needs following
We have introduced the following Chart parameters. Chart parameters are available.
### General parameters ### General parameters

2
docs/deployment/metrics.md
View file

@ -48,7 +48,7 @@ to scrape metrics from NFD, you need to pass the following values to Helm:
For more info on Helm deployment, see [Helm](helm.md). For more info on Helm deployment, see [Helm](helm.md).
We recommend setting It is recommended to specify
`--set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues=false` `--set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues=false`
when deploying prometheus-operator via Helm to enable the prometheus-operator when deploying prometheus-operator via Helm to enable the prometheus-operator
to scrape metrics from any PodMonitor. to scrape metrics from any PodMonitor.

2
docs/usage/customization-guide.md
View file

@ -316,7 +316,7 @@ vendor.io/feature4=featureValue4
After processing the above file, only `vendor.io/feature2` and After processing the above file, only `vendor.io/feature2` and
`vendor.io/feature3` would be included in the list of accepted features. `vendor.io/feature3` would be included in the list of accepted features.
> **NOTE:** The time format that we are supporting is RFC3339. Also, the `expiry-time` > **NOTE:** The time format supported is RFC3339. Also, the `expiry-time`
> tag is only evaluated in each re-discovery period, and the expiration of > tag is only evaluated in each re-discovery period, and the expiration of
> node labels is not tracked. > node labels is not tracked.