From 620ee9a0a20a4011f7f5cc784ed07d3aad053adb Mon Sep 17 00:00:00 2001
From: Alfonso Acosta <alfonso.acosta@gmail.com>
Date: Mon, 7 Mar 2016 12:19:53 +0100
Subject: [PATCH] Clarify priviledged-pods requirement in kubernetes

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9ccb0b200..e0a98bebc 100644
--- a/README.md
+++ b/README.md
@@ -176,7 +176,8 @@ Scope comes with built-in Kubernetes support. We recommend to run Scope natively
 in your Kubernetes cluster using
 [these resource definitions](https://github.com/TheNewNormal/kube-charts/tree/master/weavescope/manifests).
 
-1. If you are running a Kubernetes version lower than 1.1, make sure your
+1. Make sure your cluster allows priviledged pods (allowed by default from Kubernetes 1.1). 
+   If you are running a Kubernetes version lower than 1.1, make sure your
    cluster allows running pods in privileged mode (required by the Scope
    probes). To allow privileged pods, your API Server and all your Kubelets must
    be provided with flag `--allow_privileged` at launch time.