c81e99d98d
Automatic merge from submit-queue (batch tested with PRs 41728, 42231) Adding new tests to e2e/vsphere_volume_placement.go **What this PR does / why we need it**: Adding new tests to e2e/vsphere_volume_placement.go Below is the tests description and test steps. **Test Back-to-back pod creation/deletion with different volume sources on the same worker node** 1. Create volumes - vmdk2, vmdk1 is created in the test setup. 2. Create pod Spec - pod-SpecA with volume path of vmdk1 and NodeSelector set to label assigned to node1. 3. Create pod Spec - pod-SpecB with volume path of vmdk2 and NodeSelector set to label assigned to node1. 4. Create pod-A using pod-SpecA and wait for pod to become ready. 5. Create pod-B using pod-SpecB and wait for POD to become ready. 6. Verify volumes are attached to the node. 7. Create empty file on the volume to make sure volume is accessible. (Perform this step on pod-A and pod-B) 8. Verify file created in step 5 is present on the volume. (perform this step on pod-A and pod-B) 9. Delete pod-A and pod-B 10. Repeatedly (5 times) perform step 4 to 9 and verify associated volume's content is matching. 11. Wait for vmdk1 and vmdk2 to be detached from node. 12. Delete vmdk1 and vmdk2 **Test multiple volumes from different datastore within the same pod** 1. Create volumes - vmdk2 on non default shared datastore. 2. Create pod Spec with volume path of vmdk1 (vmdk1 is created in test setup on default datastore) and vmdk2. 3. Create pod using spec created in step-2 and wait for pod to become ready. 4. Verify both volumes are attached to the node on which pod are created. Write some data to make sure volume are accessible. 5. Delete pod. 6. Wait for vmdk1 and vmdk2 to be detached from node. 7. Create pod using spec created in step-2 and wait for pod to become ready. 8. Verify both volumes are attached to the node on which PODs are created. Verify volume contents are matching with the content written in step 4. 9. Delete POD. 10. Wait for vmdk1 and vmdk2 to be detached from node. 11. Delete vmdk1 and vmdk2 **Test multiple volumes from same datastore within the same pod** 1. Create volumes - vmdk2, vmdk1 is created in testsetup 2. Create pod Spec with volume path of vmdk1 (vmdk1 is created in test setup) and vmdk2. 3. Create pod using spec created in step-2 and wait for pod to become ready. 4. Verify both volumes are attached to the node on which pod are created. Write some data to make sure volume are accessible. 5. Delete pod. 6. Wait for vmdk1 and vmdk2 to be detached from node. 7. Create pod using spec created in step-2 and wait for pod to become ready. 8. Verify both volumes are attached to the node on which PODs are created. Verify volume contents are matching with the content written in step 4. 9. Delete POD. 10. Wait for vmdk1 and vmdk2 to be detached from node. 11. Delete vmdk1 and vmdk2 **Which issue this PR fixes** fixes # **Special notes for your reviewer**: Executed tests against K8S v1.5.3 release **Release note**: ```release-note NONE ``` cc: @kerneltime @abrarshivani @BaluDontu @tusharnt @pdhamdhere |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| cluster | ||
| cmd | ||
| docs | ||
| examples | ||
| federation | ||
| Godeps | ||
| hack | ||
| hooks | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .bazelrc | ||
| .gazelcfg.json | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| labels.yaml | ||
| LICENSE | ||
| Makefile | ||
| Makefile.generated_files | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| Vagrantfile | ||
| WORKSPACE | ||
Kubernetes
Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.
Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.
Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.
To start using Kubernetes
See our documentation on kubernetes.io.
Try our interactive tutorial.
Take a free course on Scalable Microservices with Kubernetes.
To start developing Kubernetes
The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.
If you want to build Kubernetes right away there are two options:
You have a working Go environment.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
You have a working Docker environment.
$ git clone https://github.com/kubernetes/kubernetes
$ cd kubernetes
$ make quick-release
If you are less impatient, head over to the developer's documentation.
Support
If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.
That said, if you have questions, reach out to us one way or another.