You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deploy-1.17-and-later.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ deployment.apps/snapshot-controller created
49
49
50
50
## Deployment
51
51
The simplest way to test the HostPath driver is by running the deploy.sh script corresponding to your cluster's Kubernetes version.
52
-
For example, to deploy on Kubernetes 1.32.2, use the following command:
52
+
For example, to deploy on the latest Kubernetes, use the following command:
53
53
54
54
```
55
55
# deploy hostpath driver
@@ -243,7 +243,7 @@ Events:
243
243
```
244
244
245
245
## Confirm Hostpath driver works
246
-
The Hostpath driver is configured to create new volumes under `/csi-data-dir` inside the hostpath container that is specified in the plugin StatefulSet found [here](../deploy/kubernetes-1.22-test/hostpath/csi-hostpath-plugin.yaml).
246
+
The Hostpath driver is configured to create new volumes under `/csi-data-dir` inside the hostpath container that is specified in the plugin StatefulSet found [here](../deploy/kubernetes-1.30-test/hostpath/csi-hostpath-plugin.yaml).
247
247
This path persist as long as the StatefulSet pod is up and running.
248
248
249
249
A file written in a properly mounted Hostpath volume inside an application should show up inside the Hostpath container.
0 commit comments