From 4ecb2670b7d8d479d7d8f38f9676a5d4864a6d48 Mon Sep 17 00:00:00 2001 From: Max Williams Date: Tue, 13 Nov 2018 10:50:31 +0100 Subject: [PATCH] Updating readme with configmap details Signed-off-by: Max Williams --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e3eed3e8..4aaae25c 100644 --- a/README.md +++ b/README.md @@ -117,10 +117,13 @@ The easiest way to install node-problem-detector into your cluster is to use the helm install stable/node-problem-detector ``` -Alternatively, you can edit [node-problem-detector.yaml](deployment/node-problem-detector.yaml) to fit your environment. Set `log` volume to your system log directory (used by SystemLogMonitor). For Kubernetes versions older than 1.9, use [node-problem-detector-old.yaml](deployment/node-problem-detector-old.yaml). +Or alternatively, to install node-problem-detector manually: -- Create the DaemonSet with `kubectl create -f deployment/node-problem-detector.yaml`. -- If needed, you can use a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) to overwrite the `config` directory inside the pod. +* Edit [node-problem-detector.yaml](deployment/node-problem-detector.yaml) to fit your environment. Set `log` volume to your system log directory (used by SystemLogMonitor). For Kubernetes versions older than 1.9, use [node-problem-detector-old.yaml](deployment/node-problem-detector-old.yaml). + +* If needed, you can use a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) to overwrite the `config` directory inside the pod. Edit [node-problem-detector-config.yaml](deployment/node-problem-detector-config.yaml) as required and create the `ConfigMap` with `kubectl create -f node-problem-detector-config.yaml`. + +* Create the DaemonSet with `kubectl create -f node-problem-detector.yaml`. ## Start Standalone