You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the namespace monitoring isn't created during the operation and that causes the kubectl apply to fail after jsonnet build, after that it's unclear why nothing shows up in UI
k8s-1
changed the title
customizations all namespaces is broken
customizations all namespaces fails on missing monitoring namespace
Aug 21, 2024
k8s-1
changed the title
customizations all namespaces fails on missing monitoring namespace
customizations all namespaces is broken
Aug 21, 2024
What happened?
Applied customizations all namespaces in kind cluster -> https://github.com/prometheus-operator/kube-prometheus/blob/main/docs/customizations/monitoring-all-namespaces.md, got error: resource mapping not found for name: "k8s" namespace: "monitoring" from "manifests/prometheus-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1"
Next, checked prometheus UI in http://localhost:9090/targets?search=
-> No scrape pools configured
Did you expect to see some different?
Expected to see no error, scrape pools showing up in UI
How to reproduce it (as minimally and precisely as possible):
Apply the jsonnet https://github.com/prometheus-operator/kube-prometheus/blob/main/docs/customizations/monitoring-all-namespaces.md to a clean cluster
Environment
kind/kubeadm
Prometheus Operator version:
Insert image tag or Git SHA here
app.kubernetes.io/version=0.76.0
Kubernetes version information:
kubectl version
Client Version: v1.30.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.31.0
Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, tectonic-installer, etc.
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: