Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Extend test/e2e/scheduling/nvidia-gpus.go to track resource usage of installer and device plugin containers. To support this, exports certain functions and fields in framework/resource_usage_gatherer.go so that it can be used in any e2e test to track any specified pod resource usage with the specified probe interval and duration. **What this PR does / why we need it**: We need to quantify the resource usage of the device plugin DaemonSet to make sure it can run reliably on nodes with GPUs. We also want to measure gpu driver installer resource usage to track any unexpected resource consumption during driver installation. For the later part, see a related issue https://github.com/kubernetes/features/issues/368. Example resource summary output: Oct 6 12:35:07.289: INFO: Printing summary: ResourceUsageSummary Oct 6 12:35:07.289: INFO: ResourceUsageSummary JSON { "100": [ { "Name": "nvidia-device-plugin-6kqxp/nvidia-device-plugin", "Cpu": 0.000507167, "Mem": 2134016 }, { "Name": "nvidia-device-plugin-6kqxp/nvidia-driver-installer", "Cpu": 1.915508718, "Mem": 663330816 }, { "Name": "nvidia-device-plugin-l28zc/nvidia-device-plugin", "Cpu": 0.000836256, "Mem": 2211840 }, { "Name": "nvidia-device-plugin-l28zc/nvidia-driver-installer", "Cpu": 1.916886293, "Mem": 691449856 }, { "Name": "nvidia-device-plugin-xb4vh/nvidia-device-plugin", "Cpu": 0.000515103, "Mem": 2265088 }, { "Name": "nvidia-device-plugin-xb4vh/nvidia-driver-installer", "Cpu": 1.909435982, "Mem": 832430080 } ], "50": [ { ... **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note ``` |
||
---|---|---|
.github | ||
api | ||
build | ||
cluster | ||
cmd | ||
docs | ||
examples | ||
Godeps | ||
hack | ||
logo | ||
pkg | ||
plugin | ||
staging | ||
test | ||
third_party | ||
translations | ||
vendor | ||
.bazelrc | ||
.generated_files | ||
.gitattributes | ||
.gitignore | ||
.kazelcfg.json | ||
BUILD.bazel | ||
CHANGELOG-1.2.md | ||
CHANGELOG-1.3.md | ||
CHANGELOG-1.4.md | ||
CHANGELOG-1.5.md | ||
CHANGELOG-1.6.md | ||
CHANGELOG-1.7.md | ||
CHANGELOG-1.8.md | ||
CHANGELOG-1.9.md | ||
CHANGELOG.md | ||
code-of-conduct.md | ||
CONTRIBUTING.md | ||
labels.yaml | ||
LICENSE | ||
Makefile | ||
Makefile.generated_files | ||
OWNERS | ||
OWNERS_ALIASES | ||
README.md | ||
SUPPORT.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.