Skip to content

Commit

Permalink
Update README
Browse files Browse the repository at this point in the history
  • Loading branch information
ctrox committed May 15, 2019
1 parent f80104f commit 2d3c8be
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,29 +49,29 @@ kubectl create -f storageclass.yaml

### 4. Test the S3 driver

* Create a pvc using the new storage class:
1. Create a pvc using the new storage class:

```bash
kubectl create -f pvc.yaml
```

* Check if the PVC has been bound:
2. Check if the PVC has been bound:

```bash
$ kubectl get pvc csi-s3-pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
csi-s3-pvc Bound pvc-c5d4634f-8507-11e8-9f33-0e243832354b 5Gi RWO csi-s3 9s
```

* Create a test pod which mounts your volume:
3. Create a test pod which mounts your volume:

```bash
kubectl create -f poc.yaml
```

If the pod can start, everything should be working.

* Test the mount
4. Test the mount

```bash
$ kubectl exec -ti csi-s3-test-nginx bash
Expand Down Expand Up @@ -135,16 +135,16 @@ Fore more detailed limitations consult the documentation of the different projec

### Issues while creating PVC

* Check the logs of the provisioner:
Check the logs of the provisioner:

```bash
kubectl logs -l app=csi-provisioner-s3 -c csi-s3
```

### Issues creating containers

* Ensure feature gate `MountPropagation` is not set to `false`
* Check the logs of the s3-driver:
1. Ensure feature gate `MountPropagation` is not set to `false`
2. Check the logs of the s3-driver:

```bash
kubectl logs -l app=csi-s3 -c csi-s3
Expand Down

0 comments on commit 2d3c8be

Please sign in to comment.