Files

k8s-merge-robot fe15db60f4 Merge pull request #25986 from Random-Liu/enable-node-problem-detector

Automatic merge from submit-queue

Add node problem detector as an addon pod.

```release-note
Introduce a new add-on pod NodeProblemDetector.

NodeProblemDetector is a DaemonSet running on each node, monitoring node health and reporting
node problems as NodeCondition and Event. Currently it already supports kernel log monitoring, and
will support more problem detection in the future. It is enabled by default on gce now.
```

This PR enables NodeProblemDetector as an add-on pod.

/cc @mikedanese @kubernetes/sig-node 

[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()

2016-05-22 06:17:28 -07:00

pillar

AWS kube-up: Add support for wily

2016-02-17 10:45:21 -05:00

reactor

Add ga-beacon analytics to gendocs scripts

2015-05-15 18:56:38 -07:00

salt

Merge pull request #25986 from Random-Liu/enable-node-problem-detector

2016-05-22 06:17:28 -07:00

install.sh

don't ship kube-registry-proxy and pause in tars.

2016-04-05 07:32:07 -07:00

README.md

declare azure/ubuntu/saltstack bankruptcy

2015-10-16 18:21:21 -07:00

README.md

SaltStack configuration

This is the root of the SaltStack configuration for Kubernetes. A high level overview for the Kubernetes SaltStack configuration can be found in the docs tree.

This SaltStack configuration currently applies to default configurations for Debian-on-GCE, Fedora-on-Vagrant, and Ubuntu-on-AWS. (That doesn't mean it can't be made to apply to an arbitrary configuration, but those are only the in-tree OS/IaaS combinations supported today.) As you peruse the configuration, these are shorthanded as gce, vagrant, aws in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more: