Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 3ef674188d
Merge pull request #56864 from juanvallejo/jvallejo/add-selector-kubectl-drain
Automatic merge from submit-queue (batch tested with PRs 55751, 57337, 56406, 56864, 57347). 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>.

Add pod-selector kubectl drain

**Release note**:
```release-note
Added the ability to select pods in a chosen node to be drained, based on given pod label-selector
```

This patch adds the ability to select pods in a chosen node to be drained, based on given pod label-selector. Related downstream issue: https://github.com/openshift/origin/issues/17554

Further, it removes explicit, specific, pod-controller check. The `drain` command currently fails if a pod has a controller of a `kind` [not explicitly handled in the command itself](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/drain.go#L331). This causes `drain` to be unusable if a node contains pods managed by third-party, or "unknown" controllers.

Based on [this comment](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/drain.go#L353), the expectation was to fail if a pod's controller was not found for whatever reason. I believe that the `drain` command should not care about the existence of a pod controller. It should only care whether a pod has one, and act according to that controller kind. This solves a downstream bug: https://github.com/openshift/origin/issues/17563

cc @fabianofranz @deads2k @kubernetes/sig-cli-misc
2017-12-18 18:50:45 -08:00
.github Merge pull request #54114 from xiangpengzhao/fix-pr-template 2017-10-30 18:37:06 -07:00
api Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
build gcloud docker now auths k8s.gcr.io by default 2017-12-18 09:18:34 -08:00
cluster Merge pull request #57337 from wwwtyro/rye/wait-kube-dns 2017-12-18 18:50:40 -08:00
cmd Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
docs Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
examples gcloud docker now auths k8s.gcr.io by default 2017-12-18 09:18:34 -08:00
Godeps Merge pull request #56685 from m1093782566/fix-nodeport 2017-12-18 14:45:42 -08:00
hack Merge pull request #56864 from juanvallejo/jvallejo/add-selector-kubectl-drain 2017-12-18 18:50:45 -08:00
logo Don't use strokes in the logo SVG 2017-10-12 09:38:56 -07:00
pkg Merge pull request #56864 from juanvallejo/jvallejo/add-selector-kubectl-drain 2017-12-18 18:50:45 -08:00
plugin Merge pull request #57348 from tallclair/psp-owners 2017-12-18 13:29:51 -08:00
staging Merge pull request #55751 from MrHohn/default-termination-period 2017-12-18 18:49:30 -08:00
test Merge pull request #57331 from aleksandra-malinowska/autoscaling-test-fix-13 2017-12-18 17:45:40 -08:00
third_party Update generated files 2017-11-09 12:14:08 +01:00
translations Merge pull request #47584 from zjj2wry/translate 2017-11-15 23:57:28 -08:00
vendor Merge pull request #56685 from m1093782566/fix-nodeport 2017-12-18 14:45:42 -08:00
.bazelrc
.generated_files
.gitattributes Hide openapi-spec in diffs 2017-11-04 23:16:04 -07:00
.gitignore
.kazelcfg.json
BUILD.bazel
CHANGELOG-1.2.md
CHANGELOG-1.3.md
CHANGELOG-1.4.md Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
CHANGELOG-1.5.md Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
CHANGELOG-1.6.md Use k8s.gcr.io vanity domain for container images 2017-12-18 09:18:34 -08:00
CHANGELOG-1.7.md Update CHANGELOG-1.7.md for v1.7.11. 2017-11-25 16:37:13 -05:00
CHANGELOG-1.8.md Update CHANGELOG-1.8.md for v1.8.5. 2017-12-07 09:10:33 -08:00
CHANGELOG-1.9.md Update CHANGELOG-1.9.md for v1.9.0. 2017-12-15 14:15:58 -08:00
CHANGELOG-1.10.md Add CHANGELOG-1.10.md for v1.10.0-alpha.1. 2017-12-18 13:41:16 -08:00
CHANGELOG.md Move 1.8.x release notes 2017-10-11 22:41:36 -04:00
code-of-conduct.md
CONTRIBUTING.md Pointed to community/contributors/guide/README.md 2017-12-15 22:08:34 +05:30
labels.yaml
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES Create sig-autoscaling-maintainers alias 2017-11-17 17:57:33 +01:00
README.md Reword double negative; link to readme 2017-12-07 20:58:47 -06:00
SUPPORT.md
Vagrantfile fix download link for fedora libvirt vagrant box 2017-11-18 22:26:57 +05:30
WORKSPACE

Kubernetes

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