Skip to content

Commit

Permalink
docs: typo on functional test 8
Browse files Browse the repository at this point in the history
Signed-off-by: ptx96 <[email protected]>
  • Loading branch information
ptx96 authored and David Ko committed Sep 11, 2023
1 parent 02d398e commit 914bba8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/content/manual/functional-test-cases/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ title: 5. Kubernetes
| 5 | StorageClass `nodeSelector` parameter | **Prerequisite:**<br><br>* Longhorn Node should have tags<br><br>1. Create a new StorageClass, set `nodeSelector` parameter<br>2. Create a PVC with using the new StorageClass | * New Storage class should be created<br>* Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`, volume replicas should only scheduled to Nodes with tags that match `nodeSelector` parameter tags | |
| 6 | StorageClass `recurringJobs` parameter | 1. Create a new StorageClass, set `recurringJobs` parameter<br>2. Create a PVC with using the new StorageClass<br>3. Create a pod that consumes the created PVC<br>4. Check Volume recurring jobs | * New Storage class should be created<br>* Volume should be dynamically provisioned, it’s PV/PVC should be `Bound` and attached to the pod<br>* Volume should have recurring snapshots and backups matches ones specified in `recurringJobs` StorageClass parameter | test\_statefulset\_recurring\_backup |
| 7 | StorageClass with `reclaimPolicy` parameter set to `Delete` | 1. Create a new StorageClass, set `reclaimPolicy` parameter to `Delete`<br>2. Create a PVC with using the new StorageClass<br>3. Delete the PVC | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`<br>* Deleting PVC would trigger Volume delete | |
| 8 | StorageClass with `reclaimPolicy` parameter set to `Retain` | 1. Create a new StorageClass, set `reclaimPolicy` parameter to `Delete`<br>2. Create a PVC with using the new StorageClass<br>3. Delete PVC<br>4. Delete PV | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`<br>* Deleting PVC and PV will not delete longhorn volume. | test\_kubernetes\_status |
| 8 | StorageClass with `reclaimPolicy` parameter set to `Retain` | 1. Create a new StorageClass, set `reclaimPolicy` parameter to `Retain`<br>2. Create a PVC with using the new StorageClass<br>3. Delete PVC<br>4. Delete PV | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`<br>* Deleting PVC and PV will not delete longhorn volume. | test\_kubernetes\_status |
| 9 | Static provisioning using `Default Longhorn Static StorageClass Name` Setting | 1. Update `Default Longhorn Static StorageClass Name` setting, set a new StorageClass Name, StorageClass doesn’t have to exist or be created.<br>2. Create a Volume<br>3. From Longhorn, Create a PV/PVC for the volume<br>4. Check created PV `persistentVolumeReclaimPolicy: Retain`<br>5. Create a pod consuming created PVC<br>6. Delete the pod<br>7. Delete PV<br>8. Delete PVC | * Volume should be created<br>* Volume PV should be created using new StorageClass Name defined in `Default Longhorn Static StorageClass Name` setting<br>* PVC should be consumed by the pod, volume should be accessible in the pod, write/read operations should work normally.<br>* Deleting PV/PVC will not trigger volume delete. | test\_pvc\_creation\_with\_default\_sc\_set |


Expand Down Expand Up @@ -59,4 +59,4 @@ title: 5. Kubernetes
| 18 | Power down node where the pods/workload exists<br><br>**workload type: stateful set** | * Create a workload, attach to a volume.<br>* Write some data<br>* Power down the node where the pod is running. | * The pod should get recreated on another node.<br>* The volume should get reattached.<br>* The mount point should be accessible to read and write. |
| 19 | Delete worker node one by one | | * The volume should get reattach to healthy node. | | |
| 20 | Upgrade cluster - drain set - false | 1. In Rancher - upgrade a cluster by changing the max-pods value<br>2. The cluster will go into “Updating” state<br>3. Verify upgrade completes successfully | Upgrade should finish successfully |
| 21 | Upgrade cluster - drain set - true | 1. In Rancher - upgrade a cluster by changing the max-pods value<br>2. The cluster will go into “Updating” state<br>3. Verify upgrade completes successfully | Upgrade should finish successfully |
| 21 | Upgrade cluster - drain set - true | 1. In Rancher - upgrade a cluster by changing the max-pods value<br>2. The cluster will go into “Updating” state<br>3. Verify upgrade completes successfully | Upgrade should finish successfully |

0 comments on commit 914bba8

Please sign in to comment.