hpi-schul-cloud / jitsi-deployment

Auto-scalable Jitsi Meet for Kubernetes
MIT License
215 stars 88 forks source link

Prometheus not deploying in namespace #19

Open esencia opened 4 years ago

esencia commented 4 years ago

Hi, First of all, thanks for all the work in the project. It's absolutely amazing.

After I deploy the 'development' overlay there's no prometheus deployments, only operator and adapter. I get the grafana endpoint in the ingress but there's no datasource available. No pods with tag prometheus:k8s.

kubectl get deployments -n monitoring
NAME                  READY   UP-TO-DATE   AVAILABLE   AGE
grafana               1/1     1            1           82m
kube-state-metrics    1/1     1            1           82m
prometheus-adapter    1/1     1            1           82m
prometheus-operator   1/1     1            1           82m

But there is a svc in the namespace:

NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
alertmanager-main       ClusterIP   10.43.2.2       <none>        9093/TCP                     82m
alertmanager-operated   ClusterIP   None            <none>        9093/TCP,9094/TCP,9094/UDP   81m
bbb                     ClusterIP   None            <none>        9100/TCP                     82m
grafana                 ClusterIP   10.43.191.171   <none>        3000/TCP                     82m
kube-state-metrics      ClusterIP   None            <none>        8443/TCP,9443/TCP            82m
node-exporter           ClusterIP   None            <none>        9100/TCP                     82m
prometheus-adapter      ClusterIP   10.43.58.35     <none>        443/TCP                      82m
prometheus-k8s          ClusterIP   10.43.103.217   <none>        9090/TCP                     82m
prometheus-operator     ClusterIP   None            <none>        8443/TCP                     82m

I've checked the kube-prometheus project and find the raw file of this deployment. But It doesn't works if apply the file into the namespace.

There are no prometheus pods running.

kubectl get pods -n monitoring
NAME                                   READY   STATUS    RESTARTS   AGE
alertmanager-main-0                    2/2     Running   0          87m
alertmanager-main-1                    2/2     Running   0          87m
alertmanager-main-2                    2/2     Running   0          87m
grafana-6cfc4fd6db-r2jn4               1/1     Running   0          88m
kube-state-metrics-6b7567c4c7-n54nn    3/3     Running   0          88m
node-exporter-5s8gp                    2/2     Running   0          88m
node-exporter-kdsw4                    2/2     Running   0          88m
node-exporter-rbfvk                    2/2     Running   0          88m
node-exporter-s7l5p                    2/2     Running   0          88m
node-exporter-z7nmv                    2/2     Running   0          88m
prometheus-adapter-b8d458474-s5qvd     1/1     Running   0          88m
prometheus-operator-666946c454-zcnnx   2/2     Running   0          88m

I don't apply the bbb-* files in the kustomize.

My config:

kubectl 1.19 / kustomize 3.5.4 Kubernetes 1.17.9 (with rke/rancher but with cluster deployed by kubespray I get the same error). Nodes with Ubuntu 18.04 and Local volumes MetalLB as LoadBalancer in L2 mode

Can you shed some light on this problem?

Thank you.