Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

customizations all namespaces is broken #2491

Open
k8s-1 opened this issue Aug 21, 2024 · 1 comment
Open

customizations all namespaces is broken #2491

k8s-1 opened this issue Aug 21, 2024 · 1 comment
Labels

Comments

@k8s-1
Copy link

k8s-1 commented 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.

kind delete cluster && kind create cluster --config - <<EOF
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
  - role: control-plane
  - role: worker
  - role: worker
EOF

  • Manifests:
not relevant
  • Prometheus Operator Logs:
not relevant
  • Prometheus Logs:
not relevant

Anything else we need to know?:

@k8s-1 k8s-1 added the kind/bug label Aug 21, 2024
@k8s-1
Copy link
Author

k8s-1 commented Aug 21, 2024

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 k8s-1 changed the title customizations all namespaces is broken customizations all namespaces fails on missing monitoring namespace Aug 21, 2024
@k8s-1 k8s-1 changed the title customizations all namespaces fails on missing monitoring namespace customizations all namespaces is broken Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant