Document CSI node ID annotations

Adds documentation for csi.alpha.kubernetes.io/node-id annotation used on
VolumeAttachments for finding node identifiers when CSINode object is unavailable,
and csi.volume.kubernetes.io/nodeid deprecated annotation previously used on Nodes.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: carlory <baofa.fan@daocloud.io>

Author: carlory

content/en/docs/reference/labels-annotations-taints/_index.md

@@ -354,6 +354,29 @@ The tutorial illustrates using AppArmor to restrict a container's abilities and
 The profile specified dictates the set of rules and restrictions that the containerized process must
 adhere to. This helps enforce security policies and isolation for your containers.
 
+### csi.alpha.kubernetes.io/node-id {#csi-alpha-kubernetes-io-node-id}
+
+Type: Annotation
+
+Example: `csi.alpha.kubernetes.io/node-id: "node-12345"`
+
+Used on: VolumeAttachments
+
+This annotation is used internally to find the node identifier when it can not be obtained from
+the `CSINode` object. It is populated by the CSI external-attacher sidecar container before a volume is attached. 
+
+It provides a fallback mechanism for detaching volumes when a `CSINode` object is not present.
+
+### csi.volume.kubernetes.io/nodeid (deprecated) {#csi-volume-kubernetes-io-nodeid}
+
+Type: Annotation
+
+Example: `csi.volume.kubernetes.io/nodeid: "node-12345"`
+
+Used on: Nodes
+
+This annotation was used internally to specify the identifier for a node as understood by the Container Storage Interface (CSI) driver. kubelet populated this annotation by calling the `NodeGetInfo` gRPC method of the CSI driver to retrieve the node ID during the driver registration. But it has been deprecated in favor of the `CSINode` object, which provides the same functionality via the `spec.drivers[].nodeID` field.
+
 ### internal.config.kubernetes.io/* (reserved prefix) {#internal.config.kubernetes.io-reserved-wildcard}
 
 Type: Annotation