Updating readme with configmap details

Signed-off-by: Max Williams <max.williams@deliveryhero.com>

Author: max-rocket-internet

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