From 441065c2f9edcb2b27b594ca75e9219dd88bd5bb Mon Sep 17 00:00:00 2001
From: Matt Calvert <miff2000@users.noreply.github.com>
Date: Mon, 6 Apr 2020 14:50:30 +0100
Subject: [PATCH] Correct typo in Rolebindig
---
docs/monitoring-other-namespaces.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/monitoring-other-namespaces.md b/docs/monitoring-other-namespaces.md
index 8327ed02..51f21201 100644
--- a/docs/monitoring-other-namespaces.md
+++ b/docs/monitoring-other-namespaces.md
@@ -5,14 +5,14 @@ This guide will help you monitor applications in other Namespaces. By default th
You have to give the list of the Namespaces that you want to be able to monitor.
This is done in the variable `prometheus.roleSpecificNamespaces`. You usually set this in your `.jsonnet` file when building the manifests.
-Example to create the needed `Role` and `Rolebindig` for the Namespace `foo` :
+Example to create the needed `Role` and `RoleBinding` for the Namespace `foo` :
```
local kp = (import 'kube-prometheus/kube-prometheus.libsonnet') + {
_config+:: {
namespace: 'monitoring',
prometheus+:: {
- namespaces: ["default", "kube-system","foo"],
+ namespaces: ["default", "kube-system", "foo"],
},
},
};
--
GitLab