Production-Grade Container Scheduling and Management
Go to file
Patrick Ohly 54d8f1648f e2e/storage: improve PV checking
TestDynamicProvisioning had multiple ways of choosing additional
checks:
- the PvCheck callback
- the builtin write/read check controlled by a boolean
- the snapshot testing

Complicating matters further, that builtin write/read test had been
more customizable with new fields `NodeSelector` and
`ExpectUnschedulable` which were only set by one particular test (see
https://github.com/kubernetes/kubernetes/pull/70941).

That is confusing and will only get more confusing when adding more
checks in the future. Therefore the write/read check is now a separate
function that must be enabled explicitly by tests that want to run it.
The snapshot checking is also defined only for the snapshot test.

The test that expects unschedulable pods now also checks for that
particular situation itself. Instead of testing it with two pods (the
behavior from the write/read check) that both fail to start, only a
single unschedulable pod is created.

Because node name, node selector and the `ExpectUnschedulable` were
only used for checking, it is possible to simplify `StorageClassTest`
by removing all of these fields.

Expect(err).NotTo(HaveOccurred()) is an anti-pattern in Ginkgo testing
because a test failure doesn't explain what failed (see
https://github.com/kubernetes/kubernetes/issues/34059). We avoid it
now by making the check function itself responsible for checking
errors and including more information in those checks.
2019-02-09 14:20:17 +01:00
.github Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
api Merge pull request #73540 from rlenferink/patch-5 2019-02-08 09:05:56 -08:00
build Merge pull request #73540 from rlenferink/patch-5 2019-02-08 09:05:56 -08:00
cluster Merge pull request #73540 from rlenferink/patch-5 2019-02-08 09:05:56 -08:00
cmd Merge pull request #73854 from RajatVaryani/master 2019-02-08 22:00:24 -08:00
docs Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
Godeps Merge pull request #73540 from rlenferink/patch-5 2019-02-08 09:05:56 -08:00
hack Merge pull request #73854 from RajatVaryani/master 2019-02-08 22:00:24 -08:00
logo Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
pkg Merge pull request #73659 from feiskyer/usage-nano-cores 2019-02-08 19:26:21 -08:00
plugin Merge pull request #72491 from liggitt/delegated-auth-permissions 2019-02-08 11:53:52 -08:00
staging Merge pull request #73213 from danielqsj/nodeapi 2019-02-08 13:14:25 -08:00
test e2e/storage: improve PV checking 2019-02-09 14:20:17 +01:00
third_party Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
translations Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
vendor Merge pull request #73540 from rlenferink/patch-5 2019-02-08 09:05:56 -08:00
.bazelrc
.generated_files Remove build/verify scripts for swagger 1.2 API docs, API server swagger ui / swagger 1.2 config 2019-01-15 13:33:06 -05:00
.gitattributes Remove build/verify scripts for swagger 1.2 API docs, API server swagger ui / swagger 1.2 config 2019-01-15 13:33:06 -05:00
.gitignore git ignore vendordiff.patch to avoid accidental checkin 2018-10-30 18:49:53 -04:00
.kazelcfg.json
BUILD.bazel
CHANGELOG-1.2.md
CHANGELOG-1.3.md
CHANGELOG-1.4.md replace features to enhancements 2018-12-12 11:37:21 +08:00
CHANGELOG-1.5.md replace features to enhancements 2018-12-12 11:37:21 +08:00
CHANGELOG-1.6.md replace features to enhancements 2018-12-12 11:37:21 +08:00
CHANGELOG-1.7.md replace features to enhancements 2018-12-12 11:37:21 +08:00
CHANGELOG-1.8.md replace features to enhancements 2018-12-12 11:37:21 +08:00
CHANGELOG-1.9.md Fix some types 2018-10-31 04:05:25 -04:00
CHANGELOG-1.10.md fix typo of 'kubadm' in CHANGELOG-1.10.md 2019-01-18 02:25:49 +08:00
CHANGELOG-1.11.md Merge pull request #71310 from xiezongzhe/patch-3 2019-01-25 18:32:01 -08:00
CHANGELOG-1.12.md Update CHANGELOG-1.12.md for v1.12.5. 2019-01-17 17:32:06 +00:00
CHANGELOG-1.13.md Update CHANGELOG-1.13.md for v1.13.3. 2019-02-01 21:06:28 +00:00
CHANGELOG-1.14.md Update CHANGELOG-1.14.md for v1.14.0-alpha.2. 2019-01-29 11:09:19 +00:00
CHANGELOG.md Updated a link to the latest changelog 2018-12-28 15:05:09 +13:00
code-of-conduct.md
CONTRIBUTING.md
LICENSE
Makefile
Makefile.generated_files
OWNERS Updated OWNERS files to include link to docs 2019-02-04 22:33:12 +01:00
OWNERS_ALIASES Add wgliang to sig-scheduling REVIEWERS. 2019-01-21 13:41:14 +08:00
README.md remove submit-queue from readme 2018-09-13 17:10:35 -07:00
SECURITY_CONTACTS
SUPPORT.md Clean up support doc resources 2018-09-19 07:15:43 -07:00
WORKSPACE

Kubernetes

GoDoc Widget CII Best Practices


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

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.

Analytics