github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-07 11:13:48 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #123942 from ii/promote-volume-attachment-lifecycle-test

Browse Source 
Promote e2e test for VolumeAttachment Endpoints + 7 Endpoints
This commit is contained in:
Kubernetes Prow Robot 2024-03-14 18:23:47 -07:00 committed by GitHub
commit 2502f898e7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 28 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
test/conformance/testdata/conformance.yaml vendored
View File

@ -3545,4 +3545,18 @@
was configured with a subpath.
release: v1.12
file: test/e2e/storage/subpath.go
- testname: VolumeAttachment, lifecycle
codename: '[sig-storage] VolumeAttachment Conformance should run through the lifecycle
of a VolumeAttachment [Conformance]'
description: Creating an initial VolumeAttachment MUST succeed. Reading the VolumeAttachment
MUST succeed with with required name retrieved. Patching a VolumeAttachment MUST
succeed with its new label found. Listing VolumeAttachment with a labelSelector
MUST succeed with a single item retrieved. Deleting a VolumeAttachment MUST succeed
and it MUST be confirmed. Creating a second VolumeAttachment MUST succeed. Updating
the second VolumentAttachment with a new label MUST succeed with its new label
found. Creating a third VolumeAttachment MUST succeed. Updating the third VolumentAttachment
with a new label MUST succeed with its new label found. Deleting both VolumeAttachments
via deleteCollection MUST succeed and it MUST be confirmed.
release: v1.30
file: test/e2e/storage/volume_attachment.go

15
test/e2e/storage/volume_attachment.go
View File

@ -39,9 +39,22 @@ var _ = utils.SIGDescribe("VolumeAttachment", func() {
f := framework.NewDefaultFramework("volumeattachment")
/*
Release: v1.30
Testname: VolumeAttachment, lifecycle
Description: Creating an initial VolumeAttachment MUST succeed. Reading the VolumeAttachment
MUST succeed with with required name retrieved. Patching a VolumeAttachment MUST
succeed with its new label found. Listing VolumeAttachment with a labelSelector
MUST succeed with a single item retrieved. Deleting a VolumeAttachment MUST succeed
and it MUST be confirmed. Creating a second VolumeAttachment MUST succeed. Updating
the second VolumentAttachment with a new label MUST succeed with its new label
found. Creating a third VolumeAttachment MUST succeed. Updating the third VolumentAttachment
with a new label MUST succeed with its new label found. Deleting both VolumeAttachments
via deleteCollection MUST succeed and it MUST be confirmed.
*/
ginkgo.Describe("Conformance", func() {
ginkgo.It("should run through the lifecycle of a VolumeAttachment", func(ctx context.Context) {
framework.ConformanceIt("should run through the lifecycle of a VolumeAttachment", func(ctx context.Context) {
vaClient := f.ClientSet.StorageV1().VolumeAttachments()