From 914bba8a34313408e7d21710004980601e29137e Mon Sep 17 00:00:00 2001 From: Pietro Terrizzi <33090752+ptx96@users.noreply.github.com> Date: Thu, 7 Sep 2023 10:53:28 +0200 Subject: [PATCH] docs: typo on functional test 8 Signed-off-by: ptx96 --- docs/content/manual/functional-test-cases/kubernetes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/manual/functional-test-cases/kubernetes.md b/docs/content/manual/functional-test-cases/kubernetes.md index 4f128a87fc..5f13237538 100644 --- a/docs/content/manual/functional-test-cases/kubernetes.md +++ b/docs/content/manual/functional-test-cases/kubernetes.md @@ -31,7 +31,7 @@ title: 5. Kubernetes | 5 | StorageClass `nodeSelector` parameter | **Prerequisite:**

* Longhorn Node should have tags

1. Create a new StorageClass, set `nodeSelector` parameter
2. Create a PVC with using the new StorageClass | * New Storage class should be created
* 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
2. Create a PVC with using the new StorageClass
3. Create a pod that consumes the created PVC
4. Check Volume recurring jobs | * New Storage class should be created
* Volume should be dynamically provisioned, it’s PV/PVC should be `Bound` and attached to the pod
* 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`
2. Create a PVC with using the new StorageClass
3. Delete the PVC | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`
* Deleting PVC would trigger Volume delete | | -| 8 | StorageClass with `reclaimPolicy` parameter set to `Retain` | 1. Create a new StorageClass, set `reclaimPolicy` parameter to `Delete`
2. Create a PVC with using the new StorageClass
3. Delete PVC
4. Delete PV | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`
* 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`
2. Create a PVC with using the new StorageClass
3. Delete PVC
4. Delete PV | * Volume should be dynamically provisioned, it’s PV/PVC should be `Bound`
* 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.
2. Create a Volume
3. From Longhorn, Create a PV/PVC for the volume
4. Check created PV `persistentVolumeReclaimPolicy: Retain`
5. Create a pod consuming created PVC
6. Delete the pod
7. Delete PV
8. Delete PVC | * Volume should be created
* Volume PV should be created using new StorageClass Name defined in `Default Longhorn Static StorageClass Name` setting
* PVC should be consumed by the pod, volume should be accessible in the pod, write/read operations should work normally.
* Deleting PV/PVC will not trigger volume delete. | test\_pvc\_creation\_with\_default\_sc\_set | @@ -59,4 +59,4 @@ title: 5. Kubernetes | 18 | Power down node where the pods/workload exists

**workload type: stateful set** | * Create a workload, attach to a volume.
* Write some data
* Power down the node where the pod is running. | * The pod should get recreated on another node.
* The volume should get reattached.
* 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
2. The cluster will go into “Updating” state
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
2. The cluster will go into “Updating” state
3. Verify upgrade completes successfully | Upgrade should finish successfully | \ No newline at end of file +| 21 | Upgrade cluster - drain set - true | 1. In Rancher - upgrade a cluster by changing the max-pods value
2. The cluster will go into “Updating” state
3. Verify upgrade completes successfully | Upgrade should finish successfully |