Lightweight Kubernetes
 
 
 
 
Go to file
Kubernetes Submit Queue a57967f47b Merge pull request #41436 from dashpole/status_bug
Automatic merge from submit-queue

Fix bug in status manager TerminatePod

In TerminatePod, we previously pass pod.Status to updateStatusInternal.  This is a bug, since it is the original status that we are given.  Not only does it skip updates made to container statuses, but in some cases it reverted the pod's status to an earlier version, since it was being passed a stale status initially.

This was the case in #40239 and #41095.  As shown in #40239, the pod's status is set to running after it is set to failed, occasionally causing very long delays in pod deletion since we have to wait for this to be corrected.

This PR fixes the bug, adds some helpful debugging statements, and adds a unit test for TerminatePod (which for some reason didnt exist before?).

@kubernetes/sig-node-bugs @vish @Random-Liu
2017-02-14 21:03:31 -08:00
.github Fix issue template to read more clearly 2017-01-27 10:15:06 -07:00
Godeps Update generated files 2017-01-29 21:41:45 +01:00
api Merge pull request #41184 from liggitt/subject-apigroup 2017-02-13 21:07:10 -08:00
build remove kube-aggregator from bazel until we can build it 2017-02-14 14:57:52 -05:00
cluster Merge pull request #41407 from Crassirostris/fluentd-gcp-sysmted-fix 2017-02-14 13:04:21 -08:00
cmd Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
docs Merge pull request #41184 from liggitt/subject-apigroup 2017-02-13 21:07:10 -08:00
examples Merge pull request #41412 from a-robinson/test 2017-02-14 15:30:20 -08:00
federation Merge pull request #41216 from marun/kubefed-auto-bind-flags 2017-02-14 15:29:58 -08:00
hack Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
hooks Fix spelling in package naming linter error message 2016-12-20 15:48:14 -05:00
logo Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
pkg Merge pull request #41436 from dashpole/status_bug 2017-02-14 21:03:31 -08:00
plugin Merge pull request #41155 from liggitt/reconcile 2017-02-14 19:54:14 -08:00
staging Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
test Merge pull request #40934 from dashpole/density_test_cadvisor 2017-02-14 17:40:32 -08:00
third_party Update generated files 2017-01-25 19:49:45 +01:00
translations Extract strings for translation. 2017-02-06 22:32:01 -08:00
vendor Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
.bazelrc Add verify-gofmt as a Bazel test. 2017-02-10 17:00:28 -08:00
.gazelcfg.json Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble 2017-01-05 22:05:17 -08:00
.generated_docs Added generated docs for kubectl create role command. 2017-02-10 13:10:47 +08:00
.generated_files List generated files for the github size munger 2016-11-15 15:47:22 -08:00
.gitattributes Add -diff attributes for generated files 2016-12-08 17:12:07 -08:00
.gitignore Add verbose mode to boilerplate 2016-10-22 21:40:08 -07:00
BUILD.bazel bazel: save git version in kubernetes.tar.gz 2017-01-23 17:28:08 -08:00
CHANGELOG.md Update CHANGELOG.md for v1.6.0-alpha.2. 2017-02-14 17:38:57 -08:00
CONTRIBUTING.md updated munge-docs 2016-11-29 01:35:11 -08:00
LICENSE LICENSE: revert modifications to Apache license 2016-11-22 11:44:46 -08:00
Makefile Add verify-gofmt as a Bazel test. 2017-02-10 17:00:28 -08:00
Makefile.generated_files Remove a from each codegen path 2016-12-30 18:44:32 -08:00
OWNERS Add wojtec to global approvers 2017-01-25 11:57:00 -06:00
OWNERS_ALIASES OWNERS: Create sig-node alias 2017-01-17 16:25:40 -08:00
README.md Tidy up the main README. 2017-02-01 20:13:09 -08:00
Vagrantfile Customizable vagrant rsync args and excludes 2016-11-14 11:18:44 +01:00
WORKSPACE upgrade to latest build rules 2017-02-01 15:16:43 -08:00
code-of-conduct.md Change code of conduct to call CNCF CoC by reference 2016-10-19 13:22:35 -04:00
labels.yaml

README.md

Kubernetes

Submit Queue Widget GoDoc 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.

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