Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 7b8bb6e7d3
Merge pull request #63357 from Random-Liu/install-and-use-crictl
Automatic merge from submit-queue (batch tested with PRs 63167, 63357). 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>.

Install and use crictl in gce kube-up.sh

Download and use crictl in gce kube-up.sh.

This PR:
1. Downloads crictl `v1.0.0-beta.0` onto the node, which supports CRI v1alpha2. We'll upgrade it to `v1.0.0-beta.1` soon after the release is cut.
2. Change `kube-docker-monitor` to `kube-container-runtime-monitor`, and let it use `crictl` to do health monitoring.
3. Change `e2e-image-puller` to use `crictl`. Because of https://github.com/kubernetes/kubernetes/issues/63355, it doesn't work now. But in `crictl v1.0.0-beta.1`, we are going to statically link it, and the `e2e-image-puller` should work again.
4. Use `systemctl kill --kill-who=main` instead of `pkill`, the reason is that:
  a. `pkill docker` will send `SIGTERM` to all processes including `dockerd`, `docker-containerd`, `docker-containerd-shim`. This is not a problem for Docker 17.03 CE, because `containerd-shim` in containerd 0.2.x doesn't exit with SIGERM (see [code](https://github.com/containerd/containerd/blob/v0.2.x/containerd-shim/main.go#L123)). However, `containerd-shim` in containerd 1.0+ does exit with SIGTERM (see [code](https://github.com/containerd/containerd/blob/master/cmd/containerd-shim/main_unix.go#L200)). This means that `pkill docker` and `pkill containerd` will kill all shim processes for Docker 17.11+ and containerd 1.0+.
  b. We can use `pkill -x` instead. However, docker systemd service name is `docker`, but daemon process name is `dockerd`. We have to introduce another environment variable to specify "daemon process name". Given so, it seems easier to just use `systemctl kill` which only requires systemd service name. `systemctl kill --kill-who=main` will make sure only main process receives SIGTERM.

Signed-off-by: Lantao Liu <lantaol@google.com>

/cc @filbranden @yujuhong @feiskyer @mrunalp @kubernetes/sig-node-pr-reviews @kubernetes/sig-cluster-lifecycle-pr-reviews 

**Release note**:

```release-note
Kubernetes cluster on GCE have crictl installed now. Users can use it to help debug their node. The documentation of crictl can be found https://github.com/kubernetes-incubator/cri-tools/blob/master/docs/crictl.md.
```
2018-05-15 21:18:12 -07:00
.github modify outdate link 2018-05-03 09:23:36 +08:00
api Merge pull request #63314 from mtaufen/dkcfg-structured-status 2018-05-15 19:41:36 -07:00
build workspace mirror: add trailing newline to urls list 2018-05-07 16:52:20 -07:00
cluster Merge pull request #63357 from Random-Liu/install-and-use-crictl 2018-05-15 21:18:12 -07:00
cmd Merge pull request #63799 from luxas/kubeadm_restructure_internal_config_usage 2018-05-15 19:55:12 -07:00
docs Merge pull request #63314 from mtaufen/dkcfg-structured-status 2018-05-15 19:41:36 -07:00
Godeps Merge pull request #63332 from zhouhaibing089/exec-timeout 2018-05-15 09:04:28 -07:00
hack Merge pull request #63782 from luxas/kubeadm_own_scheme 2018-05-15 05:08:10 -07:00
logo
pkg Merge pull request #62242 from feiskyer/pod-cidr 2018-05-15 19:55:19 -07:00
plugin Prevent nodes from updating taints 2018-05-15 13:54:33 -04:00
staging Merge pull request #63314 from mtaufen/dkcfg-structured-status 2018-05-15 19:41:36 -07:00
test Merge pull request #63314 from mtaufen/dkcfg-structured-status 2018-05-15 19:41:36 -07:00
third_party Update all script to use /usr/bin/env bash in shebang 2018-04-19 13:20:13 +02:00
translations Adds initial Korean translations for kubectl 2018-05-12 11:16:49 +09:00
vendor Merge pull request #63332 from zhouhaibing089/exec-timeout 2018-05-15 09:04:28 -07:00
.bazelrc
.generated_files
.gitattributes
.gitignore Remove pkg/generated/bindata.go from the repo 2018-04-25 09:44:22 -07:00
.kazelcfg.json
BUILD.bazel
CHANGELOG-1.2.md
CHANGELOG-1.3.md
CHANGELOG-1.4.md
CHANGELOG-1.5.md
CHANGELOG-1.6.md
CHANGELOG-1.7.md Update CHANGELOG-1.7.md for v1.7.16. 2018-04-04 13:07:30 +00:00
CHANGELOG-1.8.md Update CHANGELOG-1.8.md for v1.8.13. 2018-05-15 19:34:20 +00:00
CHANGELOG-1.9.md Update CHANGELOG-1.9.md for v1.9.7. 2018-04-19 12:19:02 -04:00
CHANGELOG-1.10.md Merge pull request #61874 from Pingan2017/changelog1-10 2018-04-29 07:45:43 -07:00
CHANGELOG-1.11.md Update CHANGELOG-1.11.md for v1.11.0-alpha.2. 2018-05-02 15:47:30 +00:00
CHANGELOG.md Marks 1.10 as the current release 2018-03-26 17:08:54 -07:00
code-of-conduct.md
CONTRIBUTING.md
labels.yaml
LICENSE
Makefile
Makefile.generated_files
OWNERS root OWNERS: escape backslashes 2018-04-13 10:42:22 -07:00
OWNERS_ALIASES Add myself to sig-scheduling maintainers/approvers list. 2018-04-26 14:15:14 -04:00
README.md
SUPPORT.md
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