From 3183e363c3591e07367a8066705c5a359be8186f Mon Sep 17 00:00:00 2001 From: Moritz Wiesinger Date: Wed, 5 Jul 2023 09:59:48 +0200 Subject: [PATCH] Fix typo in Kubernetes installation docs (#643) ## Which problem is this PR solving? - fixes some typos in the jaeger operator installation guide - `ClusterBindingRole` -> `ClusterRoleBinding` --------- Signed-off-by: Moritz Wiesinger --- content/docs/1.29/operator.md | 4 ++-- content/docs/1.30/operator.md | 4 ++-- content/docs/1.31/operator.md | 4 ++-- content/docs/1.32/operator.md | 4 ++-- content/docs/1.33/operator.md | 4 ++-- content/docs/1.34/operator.md | 4 ++-- content/docs/1.35/operator.md | 4 ++-- content/docs/1.36/operator.md | 4 ++-- content/docs/1.37/operator.md | 4 ++-- content/docs/1.38/operator.md | 4 ++-- content/docs/1.39/operator.md | 4 ++-- content/docs/1.40/operator.md | 4 ++-- content/docs/1.41/operator.md | 4 ++-- content/docs/1.42/operator.md | 4 ++-- content/docs/1.43/operator.md | 4 ++-- content/docs/1.44/operator.md | 4 ++-- content/docs/1.45/operator.md | 4 ++-- content/docs/1.46/operator.md | 4 ++-- content/docs/next-release/operator.md | 4 ++-- 19 files changed, 38 insertions(+), 38 deletions(-) diff --git a/content/docs/1.29/operator.md b/content/docs/1.29/operator.md index d0fdcceb..0168c35c 100644 --- a/content/docs/1.29/operator.md +++ b/content/docs/1.29/operator.md @@ -67,7 +67,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -96,7 +96,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.30/operator.md b/content/docs/1.30/operator.md index d0fdcceb..0168c35c 100644 --- a/content/docs/1.30/operator.md +++ b/content/docs/1.30/operator.md @@ -67,7 +67,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -96,7 +96,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.31/operator.md b/content/docs/1.31/operator.md index fcb3566e..00905481 100644 --- a/content/docs/1.31/operator.md +++ b/content/docs/1.31/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.32/operator.md b/content/docs/1.32/operator.md index fcb3566e..00905481 100644 --- a/content/docs/1.32/operator.md +++ b/content/docs/1.32/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.33/operator.md b/content/docs/1.33/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.33/operator.md +++ b/content/docs/1.33/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.34/operator.md b/content/docs/1.34/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.34/operator.md +++ b/content/docs/1.34/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.35/operator.md b/content/docs/1.35/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.35/operator.md +++ b/content/docs/1.35/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.36/operator.md b/content/docs/1.36/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.36/operator.md +++ b/content/docs/1.36/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.37/operator.md b/content/docs/1.37/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.37/operator.md +++ b/content/docs/1.37/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.38/operator.md b/content/docs/1.38/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.38/operator.md +++ b/content/docs/1.38/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.39/operator.md b/content/docs/1.39/operator.md index 1cdfa072..daea1e1a 100644 --- a/content/docs/1.39/operator.md +++ b/content/docs/1.39/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.40/operator.md b/content/docs/1.40/operator.md index d6d1a7ef..9aac8439 100644 --- a/content/docs/1.40/operator.md +++ b/content/docs/1.40/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.41/operator.md b/content/docs/1.41/operator.md index d6d1a7ef..9aac8439 100644 --- a/content/docs/1.41/operator.md +++ b/content/docs/1.41/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.42/operator.md b/content/docs/1.42/operator.md index d6d1a7ef..9aac8439 100644 --- a/content/docs/1.42/operator.md +++ b/content/docs/1.42/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.43/operator.md b/content/docs/1.43/operator.md index 4f53a173..84962364 100644 --- a/content/docs/1.43/operator.md +++ b/content/docs/1.43/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.44/operator.md b/content/docs/1.44/operator.md index 4f53a173..84962364 100644 --- a/content/docs/1.44/operator.md +++ b/content/docs/1.44/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.45/operator.md b/content/docs/1.45/operator.md index 8f2e8950..a8bde9d6 100644 --- a/content/docs/1.45/operator.md +++ b/content/docs/1.45/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/1.46/operator.md b/content/docs/1.46/operator.md index 8f2e8950..a8bde9d6 100644 --- a/content/docs/1.46/operator.md +++ b/content/docs/1.46/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: diff --git a/content/docs/next-release/operator.md b/content/docs/next-release/operator.md index 8f2e8950..a8bde9d6 100644 --- a/content/docs/next-release/operator.md +++ b/content/docs/next-release/operator.md @@ -75,7 +75,7 @@ kubectl create -f https://github.com/jaegertracing/jaeger-operator/releases/down <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. At this point, there should be a `jaeger-operator` deployment available. You can view it by running the following command: @@ -104,7 +104,7 @@ oc create -f https://github.com/jaegertracing/jaeger-operator/releases/download/ <2> This installs the "Custom Resource Definition" for the `apiVersion: jaegertracing.io/v1` -The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterBindingRole` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. +The operator will be installed in cluster wide mode, if you want to only watch an specific namespace you need to change the `ClusterRole` and `ClusterRoleBinding` of the operator manifest to `Role` and `RoleBinding`, also set the `WATCH_NAMESPACE` environment variable on the jaeger operator Deployment. Once the operator is installed, grant the role `jaeger-operator` to users who should be able to install individual Jaeger instances. The following example creates a role binding allowing the user `developer` to create Jaeger instances: