e586ba3477
Automatic merge from submit-queue namespace deletion and kubelet restart tests for vSphere cloud provider **What this PR does / why we need it**: Following tests for vSphere cloud provider are added as part of this PR **Test to verifiy that a volume mounted to a pod that is deleted while the kubelet is down, unmounts volume when the kubelet returns** **Steps:** 1. Create volume (vmdk) 2. Create PV with volume path for the vmdk. 3. Create PVC to bind with PV. 4. Create a pod using the PVC. 5. Verify disk is attached to the node. and verify volume is mounted on the node. 6. Stop kubelet. 7. Delete pod. 8. Start kubelet. 9. Verify that volume mount not to be found on the node. **Test to verify that deleting the Namespace of a PVC and Pod causes the successful detach of Persistent Disk.** **Steps:** 1. Create volume (vmdk) 2. Create PV with volume path for the vmdk. 3. Create PVC to bind with PV. 4. Create a pod using the PVC. 5. Verify disk is attached to the node. 6. Delete Namespace. 7. Wait for namespace to get deleted. (Namespace deletion should trigger deletion of belonging pods) 8. Verify volume should be detached from the node. Moved test from https://github.com/kubernetes/kubernetes/pull/41976 **Test to verify that a volume mounted to a pod remains mounted after a kubelet restarts.** 1. Create volume (vmdk) 2. Create PV with volume path for the vmdk. 3. Create PVC to bind with PV. 4. Create a pod using the PVC. 5. Verify disk is attached to the node. 6. Write to the volume 7. Restart kubelet on the node on which pod is provisioned. 8. Verify that written file is accessible after kubelet restart. 9. Delete pod. 10. Delete PV, PVC 11. Wait for VMDK to detach from node. 12. Delete VMDK **Which issue this PR fixes** fixes # **Special notes for your reviewer**: **Release note**: ```release-note NONE ``` cc: @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.