Production-Grade Container Scheduling and Management
Go to file
Danielle Lancashire a8168ed543 e2e_node: Fix LocalStorage and PriorityLocalStorage eviction tests
Currently the storage eviction tests fail for a few reasons:
- They re-enter storage exhaustion after pulling the images during
  cleanup (increasing test storage reqs, and adding verification for
future diagnosis)
- They were timing out, as in practice it seems that eviction takes just
  over 10 minutes on an n1-standard in many cases. I'm raising these to
15 to provide some padding.

This should ideally bring these tests to passing on CI, as they've now
passed locally for me several times with the remote GCE env.

Follow up work involves diagnosing why these take so long, and
restructuring them to be less finicky.
2021-10-04 13:07:40 +02:00
.github
api generated swagger docs 2021-08-11 15:22:13 +02:00
build Merge pull request #104301 from serathius/etcd-image-2 2021-08-12 14:00:02 -07:00
CHANGELOG Fix typo in CHANGELOG-1.22.md 2021-08-13 20:48:33 +03:00
cluster Merge pull request #104317 from ibabou/add_termination_hook_startup_script 2021-08-12 17:50:57 -07:00
cmd Merge pull request #104338 from neolit123/1.23-use-dynamic-versions 2021-08-13 03:04:22 -07:00
docs
hack Merge pull request #103724 from claudiubelu/update-e2e-test-images-url 2021-08-12 09:10:13 -07:00
LICENSES Copy golang license to staging copies 2021-08-10 17:37:28 -04:00
logo
pkg Merge pull request #104378 from thockin/ipalloc-cleanup 2021-08-16 05:31:17 -07:00
plugin Merge pull request #103704 from robscott/endpoints-write-remove 2021-07-19 20:57:31 -07:00
staging Add unit tests for validateStructuralInvariants 2021-08-16 10:27:15 +08:00
test e2e_node: Fix LocalStorage and PriorityLocalStorage eviction tests 2021-10-04 13:07:40 +02:00
third_party Copy golang license to staging copies 2021-08-10 17:37:28 -04:00
vendor Refactor goroutine counting 2021-08-10 10:37:53 -04:00
.generated_files
.gitattributes
.gitignore
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod Merge pull request #102913 from pacoxu/upgrade-promotheus-common 2021-08-09 08:03:31 -07:00
go.sum Merge pull request #102913 from pacoxu/upgrade-promotheus-common 2021-08-09 08:03:31 -07:00
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES update instrumentation reviewers 2021-08-12 09:45:20 -07:00
README.md
SECURITY_CONTACTS
SUPPORT.md

Kubernetes (K8s)

GoPkg Widget CII Best Practices


Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides 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 your company 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 K8s

See our documentation on kubernetes.io.

Try our interactive tutorial.

Take a free course on Scalable Microservices with Kubernetes.

To use Kubernetes code as a library in other applications, see the list of published components. Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.

To start developing K8s

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.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make
You have a working Docker environment.
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release

For the full story, 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.