Workaround for kustomize bug triggered in metrics and monitoring inst…

…ructions (kubeflow#1284) * workaround for kustomize bug * removing the troublesome namespace field altogether
magdalenakuhn17 · Jan 12, 2021 · f83ca28 · f83ca28
1 parent 5581194
commit f83ca28
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/samples/metrics-and-monitoring/README.md b/docs/samples/metrics-and-monitoring/README.md
@@ -30,7 +30,7 @@ In this section, we will use a v1beta1 InferenceService sample to demonstrate ho
 1. `kubectl create ns kfserving-test`
 2. `cd docs/samples/v1beta1/sklearn`
 3. `kubectl apply -f sklearn.yaml -n kfserving-test`
-4. If you are using a Minikube based cluster, then in a separate terminal, run `minikube tunnel` and supply password if prompted.
+4. If you are using a Minikube based cluster, then in a separate terminal, run `minikube tunnel --cleanup` and supply password if prompted.
 5. In a separate terminal, follow [these instructions](https://github.com/kubeflow/kfserving/blob/master/README.md#determine-the-ingress-ip-and-ports) to find and set your ingress IP, host, and service hostname. Then, send prediction requests to the `sklearn-iris` model you created in Step 3. above as follows.
 ```
 while clear; do \

diff --git a/docs/samples/metrics-and-monitoring/prometheus/clusterrolebinding.yaml b/docs/samples/metrics-and-monitoring/prometheus/clusterrolebinding.yaml
@@ -9,4 +9,4 @@ roleRef:
 subjects:
 - kind: ServiceAccount
   name: prometheus
-  namespace: kfserving-monitoring
+