Change:
If a Node is in a cloud provider specified shutdown state, the Node gets tainted accordingly with `node.cloudprovider.kubernetes.io/shutdown` and the taint effect of `NoSchedule`. <ins> ### feature.node.kubernetes.io/* Used on: Nodes Example: `feature.node.kubernetes.io/network-sriov.capable: "true"` These features are advertised as labels in the Kubernetes Node object on nodes running NFD. All built-in labels use the feature.node.kubernetes.io label namespace and have the format `feature.node.kubernetes.io/<feature-name>: <true>`. NFD has many extension points for creating vendor and application-specific labels. For details, see the [customization guide](https://kubernetes-sigs.github.io/node-feature-discovery/v0.12/usage/customization-guide). ### nfd.node.kubernetes.io/master.version Example: `nfd.node.kubernetes.io/master.version: "v0.6.0"` Used on: Nodes For node(s) where the Node Feature Discovery (NFD) [master](https://kubernetes-sigs.github.io/node-feature-discovery/stable/usage/nfd-master.html) is scheduled, this annotation records the version of the NFD master. It is used for informative use only. ### nfd.node.kubernetes.io/worker.version Example: `nfd.node.kubernetes.io/worker.version: "v0.4.0"` Used on: Nodes This annotation records the version for a Node Feature Discovery's [worker](https://kubernetes-sigs.github.io/node-feature-discovery/stable/usage/nfd-worker.html) if there is one running on a node. It's used for informative use only. ### nfd.node.kubernetes.io/feature-labels Example: `nfd.node.kubernetes.io/feature-labels: "cpu-cpuid.ADX,cpu-cpuid.AESNI,cpu-hardware_multithreading,kernel-version.full"` Used on: Nodes This annotation records a comma-separated list of node feature labels managed by [Node Feature Discovery](https://kubernetes-sigs.github.io/node-feature-discovery/) (NFD). NFD uses this for an internal mechanism. You should not edit this annotation yourself. ### nfd.node.kubernetes.io/extended-resources Example: `nfd.node.kubernetes.io/extended-resources: "accelerator.acme.example/q500,example.com/coprocessor-fx5"` Used on: Nodes This annotation records a comma-separated list of [extended resources](/docs/concepts/configuration/manage-resources-containers/#extended-resources) managed by [Node Feature Discovery](https://kubernetes-sigs.github.io/node-feature-discovery/) (NFD). NFD uses this for an internal mechanism. You should not edit this annotation yourself. {{< note >}} These annotations only applies to nodes where NFD is running. To learn more about NFD and its components go to its official [documentation](https://kubernetes-sigs.github.io/node-feature-discovery/stable/get-started/). {{< /note >}} </ins> ### pod-security.kubernetes.io/enforce Example: `pod-security.kubernetes.io/enforce: "baseline"`

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be uses annotations matching Document these. Why is this needed I'm not sure it is. However, other official Kubernetes annotations are registered and documented in Comments /kind feature /priority awaiting-more-evidence /sig node /language en
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten We should triage this.
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
Node Feature Discovery detects additional hardware features on each node in a Kubernetes cluster so the pods with special capability requests can be placed in nodes that have those capabilities. I haven't seen any mention of NFD or an example of the four annotations in docs. So I'm uncertain if it should be registered in docs. the four annotations are : I know this issue is quite old but If there is a go-ahead I can add them, however, NFD seems quite interesting and it would be great to have an example to use this addon in the docs.
If you open a PR we can get a tech review from SIG Node.
/remove-priority awaiting-more-evidence
That's great. I'll get to work then. Thanks
/assign
I'd like to confirm, should we give explanation or reference for NFD right before the annotations and nfd-master, nfd-worker etc in the annotation? WDYT?
Here is a Preview:
please confirm:
I have raised a PR , PTAL