carlosedp / cluster-monitoring

Cluster monitoring stack for clusters based on Prometheus Operator
MIT License
740 stars 201 forks source link

no manifest files created with make #181

Open alehanderoo opened 1 month ago

alehanderoo commented 1 month ago

Describe the bug when running the command make, the manifest files are not generated.

I'm running my master node on a rockpi4:

   Static hostname: rockpi4c
         Icon name: computer
        Machine ID: 7de5b42d5d094cf3b2029468d757b64f
           Boot ID: 59ae98899cd84af3934d72cb50041cc7
  Operating System: Ubuntu 20.04.6 LTS
            Kernel: Linux 4.4.154-112-rockchip-gfdb18c8bab17
      Architecture: arm64

make vendor seems to do it's job

root@rockpi4c:/home/rock/cluster-monitoring# make vendor
rm -rf vendor
/root/go/bin/jb install
GET https://github.com/coreos/kube-prometheus/archive/17989b42aa10b1c6afa07043cb05bcd5ae492284.tar.gz 200
GET https://github.com/brancz/kubernetes-grafana/archive/57b4365eacda291b82e0d55ba7eec573a8198dda.tar.gz 200
GET https://github.com/coreos/etcd/archive/d8c8f903eee10b8391abaef7758c38b2cd393c55.tar.gz 200
GET https://github.com/ksonnet/ksonnet-lib/archive/0d2f82676817bbf9e4acf6495b2090205f323b9f.tar.gz 200
GET https://github.com/prometheus/node_exporter/archive/08ce3c6dd430deb51798826701a395e460620d60.tar.gz 200
GET https://github.com/coreos/prometheus-operator/archive/e31c69f9b5c6555e0f4a5c1f39d0f03182dd6b41.tar.gz 200
GET https://github.com/kubernetes-monitoring/kubernetes-mixin/archive/b61c5a34051f8f57284a08fe78ad8a45b430252b.tar.gz 200
GET https://github.com/kubernetes/kube-state-metrics/archive/d667979ed55ad1c4db44d331b51d646f5b903aa7.tar.gz 200
GET https://github.com/kubernetes/kube-state-metrics/archive/d667979ed55ad1c4db44d331b51d646f5b903aa7.tar.gz 200
GET https://github.com/prometheus/prometheus/archive/74207c04655e1fd93eea0e9a5d2f31b1cbc4d3d0.tar.gz 200
GET https://github.com/grafana/jsonnet-libs/archive/881db2241f0c5007c3e831caf34b0c645202b4ab.tar.gz 200
GET https://github.com/grafana/grafonnet-lib/archive/8fb95bd89990e493a8534205ee636bfcb8db67bd.tar.gz 200

When running make:

root@rockpi4c:/home/rock/cluster-monitoring# make
rm -rf manifests
./scripts/build.sh main.jsonnet /root/go/bin/jsonnet
using jsonnet from arg
+ set -o pipefail
+ rm -rf manifests
+ mkdir -p manifests/setup
++ find manifests -type f '!' -name '*.yaml'
+ find manifests -type f '!' -name '*.yaml' -delete

Which results in an empty manifests/setup folder:

root@rockpi4c:/home/rock/cluster-monitoring# make deploy
echo "Deploying stack setup manifests..."
Deploying stack setup manifests...
kubectl apply -f ./manifests/setup/
error: error reading [./manifests/setup/]: recognized file extensions are [.json .yaml .yml]
make: *** [Makefile:44: deploy] Error 1

What I have tried more with similar results:

  1. make docker
  2. make and make docker on a Raspberry pi 4 Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.28+rpt-rpi-v8

Troubleshooting

  1. Which kind of Kubernetes cluster are you using? (Kubernetes, K3s, etc)
    k3s --version
    k3s version v1.29.5+k3s1 (4e53a323)
    go version go1.21.9

installed go to be able to run the makecommand:

go version go1.22.3 linux/arm64
  1. Are all pods in "Running" state? If any is in CrashLoopback or Error, check it's logs.
    rock@rockpi4c:~$ kubectl get nodes
    NAME   STATUS   ROLES                  AGE   VERSION
    k3s1   Ready    control-plane,master   13h   v1.29.5+k3s1
    k3s2   Ready    <none>                 13h   v1.29.5+k3s1

Customizations

  1. Did you customize vars.jsonnet? Put the contents below:
...

{
      name: 'armExporter',
      enabled: true,
      file: import 'modules/arm_exporter.jsonnet',
    },

...

k3s: {
    enabled: true,
    master_ip: ['192.168.2.69'],
  },

  // Domain suffix for the ingresses
  suffixDomain: '192.168.2.69.nip.io',
carlosedp commented 1 month ago

Fixed with a8c6bba. Please test and report back.