Skip to content

Commit

Permalink
doc: lifecycle of the CSIAddonsNode
Browse files Browse the repository at this point in the history
added a document for the lifecycle of
the CSIAddonsNode object.

Signed-off-by: Madhu Rajanna <[email protected]>
  • Loading branch information
Madhu-1 committed Oct 31, 2024
1 parent dc55478 commit 9c7da84
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/csiaddonsnode.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,7 @@ spec:
- `name` contains the name of the driver. The name of the driver is in the format: `driver.csi.example.io`
- `endpoint` contains the URL that contains the name of the Pod and its Namespace that can be used by the controller to connect to.
- `nodeID` contains the ID of node to identify on which node the side-car is running.

## Lifecycle of CSIAddonsNode CR

The CSIAddonsNode custom resource (CR) is created by the sidecar that runs with the CSI driver. The owner of the CSIAddonsNode CR is the main owner of the sidecar pod, whether it's a DaemonSet or a Deployment. When the sidecar pod is deleted, the CSIAddonsNode CR is not removed; instead, it gets updated with new informations when the pod is recreated. The CSIAddonsNode CR is deleted only when the CSI driver’s Deployment or DaemonSet is deleted.

Check failure on line 24 in docs/csiaddonsnode.md

View workflow job for this annotation

GitHub Actions / codespell

informations ==> information

0 comments on commit 9c7da84

Please sign in to comment.