Brian Richardson
10/02/2022, 8:47 AMConditions:
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?Pranay
10/02/2022, 3:24 PMBrian Richardson
10/02/2022, 7:57 PMrichardsonb@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
Prashant Shahi
10/03/2022, 4:58 AMstorage
addons in microk8s
which is causing this.Brian Richardson
10/03/2022, 10:48 AMPrashant Shahi
10/03/2022, 10:56 AMdns
or else few of the pods would be stuck with init containers.