Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue dcf14add92 Merge pull request #37228 from sjenning/teardown-terminated-volumes
Automatic merge from submit-queue (batch tested with PRs 37228, 40146, 40075, 38789, 40189)

kubelet: storage: teardown terminated pod volumes

This is a continuation of the work done in https://github.com/kubernetes/kubernetes/pull/36779

There really is no reason to keep volumes for terminated pods attached on the node.  This PR extends the removal of volumes on the node from memory-backed (the current policy) to all volumes.

@pmorie raised a concern an impact debugging volume related issues if terminated pod volumes are removed.  To address this issue, the PR adds a `--keep-terminated-pod-volumes` flag the kubelet and sets it for `hack/local-up-cluster.sh`.

For consideration in 1.6.

Fixes #35406

@derekwaynecarr @vishh @dashpole

```release-note
kubelet tears down pod volumes on pod termination rather than pod deletion
```
2017-01-20 12:34:52 -08:00
.github
api Merge pull request #39446 from fraenkel/env_secrets 2017-01-19 18:53:45 -08:00
build Merge pull request #36853 from verb/init 2017-01-19 18:53:49 -08:00
cluster Merge pull request #40011 from vwfs/optional_cachebust 2017-01-20 10:48:43 -08:00
cmd Merge pull request #37228 from sjenning/teardown-terminated-volumes 2017-01-20 12:34:52 -08:00
docs Merge pull request #39446 from fraenkel/env_secrets 2017-01-19 18:53:45 -08:00
examples Merge pull request #40221 from sjenning/fix-munge-docs 2017-01-20 11:39:36 -08:00
federation Merge pull request #40170 from deads2k/client-10-restclient 2017-01-20 09:18:52 -08:00
Godeps licenses 2017-01-18 12:44:58 -08:00
hack Merge pull request #37228 from sjenning/teardown-terminated-volumes 2017-01-20 12:34:52 -08:00
hooks
logo Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
pkg Merge pull request #37228 from sjenning/teardown-terminated-volumes 2017-01-20 12:34:52 -08:00
plugin Merge pull request #40170 from deads2k/client-10-restclient 2017-01-20 09:18:52 -08:00
staging move client auth plugins 2017-01-20 08:04:53 -05:00
test Merge pull request #39033 from shyamjvs/provider-independent-kubemark 2017-01-20 09:18:54 -08:00
third_party Build release tarballs in bazel and add make bazel-release rule 2017-01-13 16:17:44 -08:00
translations
vendor mechanical results of client auth plugin 2017-01-20 08:05:18 -05:00
.gazelcfg.json
.generated_docs
.generated_files
.gitattributes
.gitignore
BUILD.bazel update staging 2017-01-20 08:04:53 -05:00
CHANGELOG.md Update CHANGELOG.md for v1.5.2. 2017-01-11 23:06:30 -08:00
code-of-conduct.md
CONTRIBUTING.md
labels.yaml
LICENSE
Makefile Add //hack:verify-boilerplate rule. 2017-01-19 11:10:48 -08:00
Makefile.generated_files
OWNERS Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
OWNERS_ALIASES OWNERS: Create sig-node alias 2017-01-17 16:25:40 -08:00
README.md
Vagrantfile
WORKSPACE Merge pull request #39898 from ixdy/bazel-release-tars 2017-01-18 14:24:48 -08:00

Kubernetes

Submit Queue Widget GoDoc Widget Coverage Status Widget

Introduction

Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications. Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF)

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.


Are you ...

Code of Conduct

The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Community

Do you want to help "shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented? ". If you are a company, you should consider joining the CNCF. For details about who's involved in CNCF and how Kubernetes plays a role, read the announcement. For general information about our community see the website community page.

Join us on social media (Twitter, Google+) and read our blog

Ask questions and help answer them on Slack or Stack Overflow

Attend our key events (kubecon, cloudnativecon, weekly community meeting)

Join a Special Interest Group (SIG)

Contribute

If you're interested in being a contributor and want to get involved in developing Kubernetes, get started with this reading:

You will then most certainly gain a lot from joining a SIG, attending the regular hangouts as well as the community meeting.

If you have an idea for a new feature, see the Kubernetes Features repository for a list of features that are coming in new releases as well as details on how to propose one.

Building Kubernetes for the impatient

If you want to build Kubernetes right away there are two options:

$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
$ 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

While there are many different channels that you can use to get hold of us (Slack, Stack Overflow, Issues, Forums/Mailing lists), you can help make sure that we are efficient in getting you the help that you need.

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. We don't bite!

Analytics