From 0116c11fa5882188c005ebf426924c2b7efaaa55 Mon Sep 17 00:00:00 2001 From: Alfonso Acosta Date: Mon, 7 Mar 2016 12:25:11 +0100 Subject: [PATCH] Rephrase Kubernetes priviledged-pods requirement --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index e0a98bebc..64cc7fbbd 100644 --- a/README.md +++ b/README.md @@ -176,11 +176,11 @@ 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. 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. +1. Make sure your cluster allows priviledged pods (required by the Scope + probes). Priviledged pods are allowed by default from Kubernetes 1.1. + If you are running an earlier version, or priviledged pods are not allowed + for any other reason, make sure your API Server and all your Kubelets are provided with + flag `--allow_privileged` at launch time. 2. Make sure your cluster supports [DaemonSets](https://github.com/kubernetes/kubernetes/blob/master/docs/design/daemon.md).