https://signoz.io logo
Join Slack
Powered by
hello. I have installed Signoz from Helm on microk...
# general
b
hello. I have installed Signoz from Helm on microk8s, but the frontend is failing to initialize:
Copy code
Conditions:
  Type              Status
  Initialized       False 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  nginx-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      signoz-frontend
    Optional:  false
  kube-api-access-z6hqd:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
It is looking for a ConfigMap called nginx-config, but there isn't one. Where does that come from?
p
@Prashant Shahi may have more insights on this
b
Copy code
richardsonb@richardsonb-cl:~/k8s/signoz$ kubectl -n platform get pv
NAME               CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                       STORAGECLASS    REASON   AGE
alertmanager-pv    100Mi      RWO            Delete           Bound    platform/storage-signoz-alertmanager-0      local-storage            4m19s
clickhouse-pv      20Gi       RWO            Delete           Bound    platform/clickhouse-pvc                     local-storage            4m19s
query-service-pv   1Gi        RWO            Delete           Bound    platform/signoz-db-signoz-query-service-0   local-storage            4m19s
zookeeper-pv       20Gi       RWO            Delete           Bound    platform/data-signoz-zookeeper-0            local-storage            4m19s
richardsonb@richardsonb-cl:~/k8s/signoz$ kubectl -n platform get pods
NAME                                               READY   STATUS    RESTARTS   AGE
chi-signoz-clickhouse-cluster-0-0-0                1/1     Running   0          3m52s
signoz-alertmanager-0                              1/1     Running   0          4m8s
signoz-clickhouse-operator-58fdc6c5d7-9m2fn        2/2     Running   0          4m8s
signoz-frontend-598788f76b-npdfv                   1/1     Running   0          4m8s
signoz-k8s-infra-otel-agent-7rfnd                  1/1     Running   0          4m8s
signoz-k8s-infra-otel-deployment-9b95b7d8d-crmjj   1/1     Running   0          4m8s
signoz-otel-collector-6874ff5c6f-s7gf5             1/1     Running   0          4m8s
signoz-otel-collector-metrics-69576859d8-c2khj     1/1     Running   0          4m8s
signoz-query-service-0                             1/1     Running   0          4m8s
signoz-zookeeper-0                                 1/1     Running   0          4m8s
none of this is in the documentation; I had to create the file volumes.yml (attached below) and create a configmap nginx-config with the contents of an nginx.conf from the source tree.
and finally, I had to create the local-storage storage class, and override the name of Clickhouse's PVC to make it all work
Either I missed something big, or the documentation needs some updating. 🙂
p
Hey @Brian Richardson 👋 It is likely that you have not enabled 
storage
addons in 
microk8s
which is causing this.
b
ah, that would explain it. I thought I might be missing something in microk8s, so I went with kubernetes.io and figured it out eventually.
p
Also, make sure to enable 
dns
or else few of the pods would be stuck with init containers.
12 Views
Open in Slack
PreviousNext
Powered by