Files

k8s-merge-robot e0707b137f Merge pull request #26827 from Random-Liu/re-enable-node-problem-detector

Automatic merge from submit-queue

Re-enable node problem detector by default

Re-enable node problem detector started in gce cluster by default.

For now, in the master node, the node problem detector will be started and do nothing (see https://github.com/kubernetes/node-problem-detector/pull/13).

But in fact, in my test cluster, the master has no extra cpu to run the node problem detector, so node problem detector is started on all nodes except master, which is what we want but not expected...

@dchen1107 
/cc @kubernetes/sig-node 
/cc @andyzheng0831 for the gci script change.

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

2016-06-04 12:33:58 -07:00

configure-helper.sh

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

2016-06-04 12:33:58 -07:00

configure.sh

GCI: correct the fix in #26363

2016-06-02 10:45:03 -07:00

health-monitor.sh

Revert "Revert "Add support for running GCI on the GCE cloud provider""

2016-05-23 00:52:08 -07:00

helper.sh

GCI: cherry-pick the fix in PR #25670

2016-05-31 21:13:15 -07:00

master.yaml

Revert "Revert "Add support for running GCI on the GCE cloud provider""

2016-05-23 00:52:08 -07:00

node.yaml

Revert "Revert "Add support for running GCI on the GCE cloud provider""

2016-05-23 00:52:08 -07:00

README.md

Revert "Revert "Add support for running GCI on the GCE cloud provider""

2016-05-23 00:52:08 -07:00

README.md

Google Container-VM Image (GCI)

GCI is a container-optimized OS image for the Google Cloud Platform (GCP). We built GCI primarily for running Google services on GCP. Unlike the open preview version of container-vm, Google Container-VM Image is based on the open source Chromium OS project, allowing us greater control over the build management, security compliance, and customizations for GCP.