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
@@ -117,20 +120,23 @@ volumesnapshotclass.snapshot.storage.k8s.io/csi-hostpath-snapclass created
117
120
118
121
The [livenessprobe side-container](https://github.com/kubernetes-csi/livenessprobe) provided by the CSI community is deployed with the CSI driver to provide the liveness checking of the CSI services.
119
122
123
+
## Modify Cluster Role
124
+
125
+
For example, if you want to modify external-resizer RBAC rules, you can do:
126
+
```
127
+
kubectl edit clusterrole external-resizer-runner
128
+
```
129
+
Replace external-resizer-runner to the role you want to modify
130
+
120
131
## Run example application and validate
121
132
122
133
Next, validate the deployment. First, ensure all expected pods are running properly including the external attacher, provisioner, snapshotter and the actual hostpath driver plugin:
123
134
124
135
```shell
125
136
$ kubectl get pods
126
-
NAME READY STATUS RESTARTS AGE
127
-
csi-hostpath-attacher-0 1/1 Running 0 4m21s
128
-
csi-hostpath-provisioner-0 1/1 Running 0 4m19s
129
-
csi-hostpath-resizer-0 1/1 Running 0 4m19s
130
-
csi-hostpath-snapshotter-0 1/1 Running 0 4m18s
131
-
csi-hostpath-socat-0 1/1 Running 0 4m18s
132
-
csi-hostpathplugin-0 3/3 Running 0 4m20s
133
-
snapshot-controller-0 1/1 Running 0 4m37s
137
+
NAME READY STATUS RESTARTS AGE
138
+
csi-hostpath-socat-0 1/1 Running 0 42m
139
+
csi-hostpathplugin-0 8/8 Running 0 42m
134
140
```
135
141
136
142
From the root directory, deploy the application pods including a storage class, a PVC, and a pod which mounts a volume using the Hostpath driver found in directory `./examples`:
0 commit comments