Basic Helm Install setting signoz.service.port fails

[cloudcodger]

Attempting to do a vary basic install of SigNoz on a 3 node kubernetes cluster.

Steps to Reproduce

• Install SigNoz with basic Helm values (to use LoadBalancer port 80)
• Check running pods

Environment

• Kubernetes version: v1.33.4+k0s
• Helm chart version: 0.93.1
• Installation method: Helm
• Storage Class: ceph-rbd

Expected Behavior

All pods should be running.

Actual Behavior

The signoz pod goes into CrashLoopBackOff.

Helm Values Used

global:
  storageClass: ceph-rbd

clickhouse:
  installCustomStorageClass: true

signoz:
  replicaCount: 3
  service:
    annotations:
      metallb.universe.tf/loadBalancerIPs: "192.168.6.177"  # Your desired IP
    type: LoadBalancer
    port: 80

otelCollector:
  service:
    type: LoadBalancer
    loadBalancerIP: "192.168.6.175"

Logs from signoz-0 pod.

% kubectl logs signoz-0 -n signoz
Defaulted container "signoz" out of: signoz, signoz-init (init)

                       -**********=
                  .::-=+**********+=--:.
              .-=*******++=-----==+******=-.
           :-+*******=:.            :-+******=:
        .-********+:                   .=*******=.
{"timestamp":"2025-09-28T16:47:09.734634544Z","level":"WARN","code":{"function":"github.com/SigNoz/signoz/pkg/signoz.mergeAndEnsureBackwardCompatibility","file":"/home/runner/work/signoz/signoz/pkg/signoz/config.go","line":243},"msg":"[Deprecated] flag --config is deprecated for passing prometheus config. The flag will be used for passing the entire SigNoz config. More details can be found at https://github.com/SigNoz/signoz/issues/6805."}
{"timestamp":"2025-09-28T16:47:09.734726709Z","level":"WARN","code":{"function":"github.com/SigNoz/signoz/pkg/signoz.mergeAndEnsureBackwardCompatibility","file":"/home/runner/work/signoz/signoz/pkg/signoz/config.go","line":295},"msg":"[Deprecated] flag --flux-interval is deprecated and scheduled for removal. Please use SIGNOZ_QUERIER_FLUX__INTERVAL instead."}
{"timestamp":"2025-09-28T16:47:09.73474347Z","level":"WARN","code":{"function":"github.com/SigNoz/signoz/pkg/signoz.mergeAndEnsureBackwardCompatibility","file":"/home/runner/work/signoz/signoz/pkg/signoz/config.go","line":305},"msg":"[Deprecated] flag --flux-interval-for-trace-detail is deprecated and scheduled for complete removal. Please use SIGNOZ_QUERIER_FLUX__INTERVAL instead."}
{"timestamp":"2025-09-28T16:47:09.734755368Z","level":"WARN","code":{"function":"github.com/SigNoz/signoz/pkg/signoz.mergeAndEnsureBackwardCompatibility","file":"/home/runner/work/signoz/signoz/pkg/signoz/config.go","line":309},"msg":"[Deprecated] flag --cluster is deprecated and scheduled for removal. Please use SIGNOZ_TELEMETRYSTORE_CLICKHOUSE_CLUSTER instead."}
{"timestamp":"2025-09-28T16:47:09.73486034Z","level":"ERROR","code":{"function":"github.com/SigNoz/signoz/cmd.NewJWTSecret","file":"/home/runner/work/signoz/signoz/cmd/config.go","line":37},"msg":"🚨 CRITICAL SECURITY ISSUE: No JWT secret key specified!","error":"SIGNOZ_JWT_SECRET environment variable is not set. This has dire consequences for the security of the application. Without a JWT secret, user sessions are vulnerable to tampering and unauthorized access. Please set the SIGNOZ_JWT_SECRET environment variable immediately. For more information, please refer to https://github.com/SigNoz/signoz/issues/8400."}
      :+********+:                       .=*******+:
    .+*********+   :+***+.                 -********+:
   -**********+.  .****=                    =*********=      ____  _             _   _               ____  _       _   _
 .************:   +****                      +**********:   / ___|| |_ __ _ _ __| |_(_)_ __   __ _  / ___|(_) __ _| \ | | ___ ____
.************+   .----:                      -***********-  \___ \| __/ _` | '__| __| | '_ \ / _` | \___ \| |/ _` |  \| |/ _ \_  /
*************=                               :************.  ___) | || (_| | |  | |_| | | | | (_| |  ___) | | (_| | |\  | (_) / / _ _ _
:************+    ----:                      -***********=  |____/ \__\__,_|_|   \__|_|_| |_|\__, | |____/|_|\__, |_| \_|\___/___(_|_|_)
 :************.   *****                      +**********:                                    |___/           |___/
  .=**********+   :****=                    -*********+.    Version: v0.96.1 (enterprise) [Copyright 2025 SigNoz, All rights reserved]
    :+*********+   :+***+                  -********+:
      :+********+.                        =*******+-
        :=********=.                    -*******=:
           :=*******+-.             .-+******=-.
              :-+*******+=--:::--=+******+=:
                  .:-==+***********+=-::
                       :**********=

{"timestamp":"2025-09-28T16:47:09.735612993Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/signoz.New","file":"/home/runner/work/signoz/signoz/pkg/signoz/signoz.go","line":75},"msg":"starting signoz","version":"v0.96.1","variant":"enterprise","commit":"2c19f01","branch":"v0.96.1","go":"go1.24.7","timestamp":"2025-09-25T15:18:31Z"}
{"timestamp":"2025-09-28T16:47:09.735815398Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/sqlstore/sqlitesqlstore.New","file":"/home/runner/work/signoz/signoz/pkg/sqlstore/sqlitesqlstore/provider.go","line":44},"msg":"connected to sqlite","logger":"github.com/SigNoz/signoz/pkg/sqlitesqlstore","path":"/var/lib/signoz/signoz.db"}
{"timestamp":"2025-09-28T16:47:09.741769837Z","level":"ERROR","code":{"function":"github.com/prometheus/prometheus/promql.NewActiveQueryTracker","file":"/home/runner/go/pkg/mod/github.com/prometheus/prometheus@v0.304.1/promql/query_logger.go","line":137},"msg":"Failed to create directory for logging active queries","logger":"github.com/SigNoz/signoz/pkg/prometheus/clickhouseprometheus"}
{"timestamp":"2025-09-28T16:47:09.769082207Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/sqlmigrator.(*migrator).Migrate","file":"/home/runner/work/signoz/signoz/pkg/sqlmigrator/migrator.go","line":44},"msg":"starting sqlstore migrations","logger":"github.com/SigNoz/signoz/pkg/sqlmigrator","dialect":"sqlite"}
{"timestamp":"2025-09-28T16:47:09.851851869Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/sqlmigrator.(*migrator).Lock","file":"/home/runner/work/signoz/signoz/pkg/sqlmigrator/migrator.go","line":91},"msg":"acquired migration lock","logger":"github.com/SigNoz/signoz/pkg/sqlmigrator","dialect":"sqlite"}
{"timestamp":"2025-09-28T16:47:09.852553863Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/sqlmigrator.(*migrator).Migrate","file":"/home/runner/work/signoz/signoz/pkg/sqlmigrator/migrator.go","line":61},"msg":"no new migrations to run (database is up to date)","logger":"github.com/SigNoz/signoz/pkg/sqlmigrator","dialect":"sqlite"}
{"level":"info","timestamp":"2025-09-28T16:47:14.932Z","caller":"app/server.go:367","msg":"rules manager is ready"}
{"level":"info","timestamp":"2025-09-28T16:47:14.939Z","caller":"app/server.go:257","msg":"Query server started listening on 0.0.0.0:8080..."}
{"timestamp":"2025-09-28T16:47:14.940021808Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Start.func1","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":50},"msg":"starting service","pkg":"go.signoz.io/pkg/factory","service":"analytics"}
{"level":"info","timestamp":"2025-09-28T16:47:14.940Z","caller":"app/server.go:277","msg":"Starting HTTP server","port":8080,"addr":"0.0.0.0:8080"}
{"level":"info","timestamp":"2025-09-28T16:47:14.940Z","caller":"app/server.go:289","msg":"Starting pprof server","addr":"0.0.0.0:6060"}
{"level":"info","timestamp":"2025-09-28T16:47:14.940Z","caller":"app/server.go:298","msg":"Starting OpAmp Websocket server","addr":"0.0.0.0:4320"}
{"timestamp":"2025-09-28T16:47:14.940507647Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Start.func1","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":50},"msg":"starting service","pkg":"go.signoz.io/pkg/factory","service":"licensing"}
{"timestamp":"2025-09-28T16:47:14.940602624Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Start.func1","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":50},"msg":"starting service","pkg":"go.signoz.io/pkg/factory","service":"instrumentation"}
{"timestamp":"2025-09-28T16:47:14.940651121Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Start.func1","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":50},"msg":"starting service","pkg":"go.signoz.io/pkg/factory","service":"alertmanager"}
{"timestamp":"2025-09-28T16:47:14.940752613Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Start.func1","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":50},"msg":"starting service","pkg":"go.signoz.io/pkg/factory","service":"statsreporter"}

[Nageshbansal]

Hey @cloudcodger, please keep the replicaCount for Signoz to be 1

[cloudcodger]

Hey @cloudcodger, please keep the replicaCount for Signoz to be 1

@Nageshbansal,

It would be very helpful to know why. I would expect that a requirement of every micro-service is that you can run multiple replicas. If that is not possible, a good explanation of the limitation needs to be placed in the values.yaml file so that people know not to change it.

Having said that. I changed my manifests/signoz-custom-values.yml to be:

global:
  storageClass: ceph-rbd

clickhouse:
  installCustomStorageClass: true

signoz:
  service:
    annotations:
      metallb.universe.tf/loadBalancerIPs: "192.168.6.177"  # Your desired IP
    type: LoadBalancer
    port: 80

otelCollector:
  replicaCount: 3
  service:
    annotations:
      metallb.universe.tf/loadBalancerIPs: "192.168.6.175"  # Your desired IP
    type: LoadBalancer

And I get the same results.

% kubectl get pods -n signoz
NAME                                          READY   STATUS             RESTARTS        AGE
chi-signoz-clickhouse-cluster-0-0-0           1/1     Running            0               12m
signoz-0                                      0/1     CrashLoopBackOff   6 (2m43s ago)   12m
signoz-clickhouse-operator-554f9bcb98-bfpb9   2/2     Running            2 (12m ago)     12m
signoz-otel-collector-7576779f8c-95d9s        1/1     Running            0               12m
signoz-otel-collector-7576779f8c-cnskk        1/1     Running            0               12m
signoz-otel-collector-7576779f8c-zhgjl        1/1     Running            0               12m
signoz-schema-migrator-async-init-8zsqt       0/1     Completed          0               12m
signoz-schema-migrator-sync-init-ncx9n        0/1     Completed          0               12m
signoz-zookeeper-0                            1/1     Running            0               12m

[cloudcodger]

In an attempt to test an even more basic configuration, I have also tried removing the otelCollector.replicaCount: 3 and get the same results.

[Nageshbansal]

Can you check the Kubernetes events for the signoz-0 pod? I’m not sure why it’s going into a CrashLoopBackOff. Also, could you verify if the logs in the Signoz pod match the ones shared earlier, or if there are any new logs appearing there?

[cloudcodger]

I just tried to deploy this again using the command helm upgrade --install signoz signoz/signoz --namespace signoz --create-namespace --wait --timeout 1h -f manifests/signoz-custom-values.yml, which eventually will time out. Below is the output of events. I'm not sure what I should be looking at here, but I don't see any obvious issues. The signoz-0 pod, eventually goes into CrashLoopBackOff as before.

% kubectl get events -n signoz
LAST SEEN   TYPE      REASON                   OBJECT                                                                                MESSAGE
11m         Warning   FailedScheduling         pod/chi-signoz-clickhouse-cluster-0-0-0                                               0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Warning   FailedScheduling         pod/chi-signoz-clickhouse-cluster-0-0-0                                               0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Normal    Scheduled                pod/chi-signoz-clickhouse-cluster-0-0-0                                               Successfully assigned signoz/chi-signoz-clickhouse-cluster-0-0-0 to work6
11m         Normal    SuccessfulAttachVolume   pod/chi-signoz-clickhouse-cluster-0-0-0                                               AttachVolume.Attach succeeded for volume "pvc-8e5aad7d-2cfb-4ac8-a754-cdd9e8556f69"
10m         Normal    Pulled                   pod/chi-signoz-clickhouse-cluster-0-0-0                                               Container image "docker.io/alpine:3.18.2" already present on machine
10m         Normal    Created                  pod/chi-signoz-clickhouse-cluster-0-0-0                                               Created container: signoz-clickhouse-udf-init
10m         Normal    Started                  pod/chi-signoz-clickhouse-cluster-0-0-0                                               Started container signoz-clickhouse-udf-init
10m         Normal    Pulled                   pod/chi-signoz-clickhouse-cluster-0-0-0                                               Container image "docker.io/clickhouse/clickhouse-server:25.5.6" already present on machine
10m         Normal    Created                  pod/chi-signoz-clickhouse-cluster-0-0-0                                               Created container: clickhouse
10m         Normal    Started                  pod/chi-signoz-clickhouse-cluster-0-0-0                                               Started container clickhouse
11m         Normal    SuccessfulCreate         statefulset/chi-signoz-clickhouse-cluster-0-0                                         create Claim data-volumeclaim-template-chi-signoz-clickhouse-cluster-0-0-0 Pod chi-signoz-clickhouse-cluster-0-0-0 in StatefulSet chi-signoz-clickhouse-cluster-0-0 success
11m         Normal    SuccessfulCreate         statefulset/chi-signoz-clickhouse-cluster-0-0                                         create Pod chi-signoz-clickhouse-cluster-0-0-0 in StatefulSet chi-signoz-clickhouse-cluster-0-0 successful
10m         Info      ReconcileInProgress      clickhouseinstallation/signoz-clickhouse                                              remove items scheduled for deletion
10m         Info      ReconcileCompleted       clickhouseinstallation/signoz-clickhouse                                              Reconcile Host 0-0 completed. ClickHouse version running: 25.5.6.14
10m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Tables added successfully on shard/host:0/0 cluster:cluster
11m         Info      ReconcileStarted         clickhouseinstallation/signoz-clickhouse                                              reconcile started, task id: 2883ea28-dbc2-4d57-97f7-39fdfcc1500d
10m         Info      ProgressHostsCompleted   clickhouseinstallation/signoz-clickhouse                                              ProgressHostsCompleted: 1 of 1
10m         Info      UpdateCompleted          clickhouseinstallation/signoz-clickhouse                                              Update ConfigMap signoz/chi-signoz-clickhouse-common-configd
10m         Info      UpdateCompleted          clickhouseinstallation/signoz-clickhouse                                              Update ConfigMap signoz/chi-signoz-clickhouse-common-configd
10m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create StatefulSet signoz/chi-signoz-clickhouse-cluster-0-0 - completed
10m         Info      CreateStarted            clickhouseinstallation/signoz-clickhouse                                              Adding tables on shard/host:0/0 cluster:cluster
11m         Info      CreateStarted            clickhouseinstallation/signoz-clickhouse                                              Create StatefulSet signoz/chi-signoz-clickhouse-cluster-0-0 - started
11m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create ConfigMap signoz/chi-signoz-clickhouse-common-configd
11m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create ConfigMap signoz/chi-signoz-clickhouse-deploy-confd-cluster-0-0
10m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create Service signoz/signoz-clickhouse
10m         Info      ReconcileInProgress      clickhouseinstallation/signoz-clickhouse                                              add CHI to monitoring
11m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create ConfigMap signoz/chi-signoz-clickhouse-common-usersd
10m         Info      ReconcileCompleted       clickhouseinstallation/signoz-clickhouse                                              reconcile completed successfully, task id: 2883ea28-dbc2-4d57-97f7-39fdfcc1500d
10m         Info      ReconcileInProgress      clickhouseinstallation/signoz-clickhouse                                              remove items scheduled for deletion
11m         Info      ReconcileStarted         clickhouseinstallation/signoz-clickhouse                                              Reconcile Host 0-0 started
10m         Info      CreateCompleted          clickhouseinstallation/signoz-clickhouse                                              Create Service signoz/chi-signoz-clickhouse-cluster-0-0
11m         Normal    ExternalProvisioning     persistentvolumeclaim/data-signoz-zookeeper-0                                         Waiting for a volume to be created either by the external provisioner 'rook-ceph.rbd.csi.ceph.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
11m         Normal    Provisioning             persistentvolumeclaim/data-signoz-zookeeper-0                                         External provisioner is provisioning volume for claim "signoz/data-signoz-zookeeper-0"
11m         Normal    ProvisioningSucceeded    persistentvolumeclaim/data-signoz-zookeeper-0                                         Successfully provisioned volume pvc-302fcf36-8929-452a-abe1-121add70ec8e
11m         Normal    ExternalProvisioning     persistentvolumeclaim/data-volumeclaim-template-chi-signoz-clickhouse-cluster-0-0-0   Waiting for a volume to be created either by the external provisioner 'rook-ceph.rbd.csi.ceph.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
11m         Normal    Provisioning             persistentvolumeclaim/data-volumeclaim-template-chi-signoz-clickhouse-cluster-0-0-0   External provisioner is provisioning volume for claim "signoz/data-volumeclaim-template-chi-signoz-clickhouse-cluster-0-0-0"
11m         Normal    ProvisioningSucceeded    persistentvolumeclaim/data-volumeclaim-template-chi-signoz-clickhouse-cluster-0-0-0   Successfully provisioned volume pvc-8e5aad7d-2cfb-4ac8-a754-cdd9e8556f69
11m         Warning   FailedScheduling         pod/signoz-0                                                                          0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Warning   FailedScheduling         pod/signoz-0                                                                          0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Normal    Scheduled                pod/signoz-0                                                                          Successfully assigned signoz/signoz-0 to work3
11m         Normal    SuccessfulAttachVolume   pod/signoz-0                                                                          AttachVolume.Attach succeeded for volume "pvc-088f47c1-a93f-490e-9b90-1f871b6a3257"
11m         Normal    Pulled                   pod/signoz-0                                                                          Container image "docker.io/busybox:1.35" already present on machine
11m         Normal    Created                  pod/signoz-0                                                                          Created container: signoz-init
11m         Normal    Started                  pod/signoz-0                                                                          Started container signoz-init
9m39s       Normal    Pulling                  pod/signoz-0                                                                          Pulling image "docker.io/signoz/signoz:v0.96.1"
9m27s       Normal    Pulled                   pod/signoz-0                                                                          Successfully pulled image "docker.io/signoz/signoz:v0.96.1" in 12.204s (12.204s including waiting). Image size: 61932369 bytes.
4m31s       Normal    Created                  pod/signoz-0                                                                          Created container: signoz
5m31s       Normal    Started                  pod/signoz-0                                                                          Started container signoz
4m22s       Warning   Unhealthy                pod/signoz-0                                                                          Liveness probe failed: Get "http://10.244.4.30:80/api/v1/health": dial tcp 10.244.4.30:80: connect: connection refused
7m32s       Warning   Unhealthy                pod/signoz-0                                                                          Readiness probe failed: Get "http://10.244.4.30:80/api/v1/health?live=1": dial tcp 10.244.4.30:80: connect: connection refused
4m32s       Normal    Killing                  pod/signoz-0                                                                          Container signoz failed liveness probe, will be restarted
4m32s       Normal    Pulled                   pod/signoz-0                                                                          Container image "docker.io/signoz/signoz:v0.96.1" already present on machine
11m         Normal    NoPods                   poddisruptionbudget/signoz-clickhouse-cluster                                         No matching pods found
11m         Normal    Scheduled                pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Successfully assigned signoz/signoz-clickhouse-operator-554f9bcb98-vf7b4 to work6
11m         Normal    Pulled                   pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Container image "docker.io/altinity/clickhouse-operator:0.21.2" already present on machine
11m         Normal    Created                  pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Created container: operator
11m         Normal    Started                  pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Started container operator
11m         Normal    Pulled                   pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Container image "docker.io/altinity/metrics-exporter:0.21.2" already present on machine
10m         Normal    Created                  pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Created container: metrics-exporter
10m         Normal    Started                  pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Started container metrics-exporter
11m         Warning   BackOff                  pod/signoz-clickhouse-operator-554f9bcb98-vf7b4                                       Back-off restarting failed container metrics-exporter in pod signoz-clickhouse-operator-554f9bcb98-vf7b4_signoz(98a417f8-5f3c-4090-a76c-ff37c808a7d1)
11m         Normal    SuccessfulCreate         replicaset/signoz-clickhouse-operator-554f9bcb98                                      Created pod: signoz-clickhouse-operator-554f9bcb98-vf7b4
11m         Normal    ScalingReplicaSet        deployment/signoz-clickhouse-operator                                                 Scaled up replica set signoz-clickhouse-operator-554f9bcb98 from 0 to 1
11m         Normal    Provisioning             persistentvolumeclaim/signoz-db-signoz-0                                              External provisioner is provisioning volume for claim "signoz/signoz-db-signoz-0"
11m         Normal    ExternalProvisioning     persistentvolumeclaim/signoz-db-signoz-0                                              Waiting for a volume to be created either by the external provisioner 'rook-ceph.rbd.csi.ceph.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
11m         Normal    ProvisioningSucceeded    persistentvolumeclaim/signoz-db-signoz-0                                              Successfully provisioned volume pvc-088f47c1-a93f-490e-9b90-1f871b6a3257
11m         Normal    Scheduled                pod/signoz-otel-collector-7576779f8c-2dj2n                                            Successfully assigned signoz/signoz-otel-collector-7576779f8c-2dj2n to work3
11m         Normal    Pulled                   pod/signoz-otel-collector-7576779f8c-2dj2n                                            Container image "docker.io/groundnuty/k8s-wait-for:v2.0" already present on machine
11m         Normal    Created                  pod/signoz-otel-collector-7576779f8c-2dj2n                                            Created container: signoz-otel-collector-migrate-init
11m         Normal    Started                  pod/signoz-otel-collector-7576779f8c-2dj2n                                            Started container signoz-otel-collector-migrate-init
6m16s       Normal    Pulled                   pod/signoz-otel-collector-7576779f8c-2dj2n                                            Container image "docker.io/signoz/signoz-otel-collector:v0.129.6" already present on machine
6m15s       Normal    Created                  pod/signoz-otel-collector-7576779f8c-2dj2n                                            Created container: collector
6m15s       Normal    Started                  pod/signoz-otel-collector-7576779f8c-2dj2n                                            Started container collector
11m         Normal    SuccessfulCreate         replicaset/signoz-otel-collector-7576779f8c                                           Created pod: signoz-otel-collector-7576779f8c-2dj2n
11m         Normal    IPAllocated              service/signoz-otel-collector                                                         Assigned IP ["192.168.6.175"]
11m         Warning   deprecatedAnnotation     service/signoz-otel-collector                                                         Service uses deprecated annotation metallb.universe.tf/loadBalancerIPs
11m         Normal    ScalingReplicaSet        deployment/signoz-otel-collector                                                      Scaled up replica set signoz-otel-collector-7576779f8c from 0 to 1
6m3s        Normal    nodeAssigned             service/signoz-otel-collector                                                         announcing from node "work5" with protocol "layer2"
11m         Normal    Scheduled                pod/signoz-schema-migrator-async-init-6762m                                           Successfully assigned signoz/signoz-schema-migrator-async-init-6762m to work3
11m         Normal    Pulled                   pod/signoz-schema-migrator-async-init-6762m                                           Container image "docker.io/busybox:1.35" already present on machine
11m         Normal    Created                  pod/signoz-schema-migrator-async-init-6762m                                           Created container: schema-migrator-async-init
11m         Normal    Started                  pod/signoz-schema-migrator-async-init-6762m                                           Started container schema-migrator-async-init
9m37s       Normal    Pulled                   pod/signoz-schema-migrator-async-init-6762m                                           Container image "docker.io/clickhouse/clickhouse-server:25.5.6" already present on machine
9m37s       Normal    Created                  pod/signoz-schema-migrator-async-init-6762m                                           Created container: schema-migrator-async-ch-ready
9m37s       Normal    Started                  pod/signoz-schema-migrator-async-init-6762m                                           Started container schema-migrator-async-ch-ready
9m35s       Normal    Pulled                   pod/signoz-schema-migrator-async-init-6762m                                           Container image "docker.io/groundnuty/k8s-wait-for:v2.0" already present on machine
9m34s       Normal    Created                  pod/signoz-schema-migrator-async-init-6762m                                           Created container: schema-migrator-async-wait-for-sync
9m32s       Normal    Started                  pod/signoz-schema-migrator-async-init-6762m                                           Started container schema-migrator-async-wait-for-sync
6m16s       Normal    Pulled                   pod/signoz-schema-migrator-async-init-6762m                                           Container image "docker.io/signoz/signoz-schema-migrator:v0.129.6" already present on machine
6m15s       Normal    Created                  pod/signoz-schema-migrator-async-init-6762m                                           Created container: schema-migrator
6m15s       Normal    Started                  pod/signoz-schema-migrator-async-init-6762m                                           Started container schema-migrator
11m         Normal    SuccessfulCreate         job/signoz-schema-migrator-async-init                                                 Created pod: signoz-schema-migrator-async-init-6762m
5m50s       Normal    Completed                job/signoz-schema-migrator-async-init                                                 Job completed
11m         Normal    Scheduled                pod/signoz-schema-migrator-sync-init-9wrp7                                            Successfully assigned signoz/signoz-schema-migrator-sync-init-9wrp7 to work3
11m         Normal    Pulled                   pod/signoz-schema-migrator-sync-init-9wrp7                                            Container image "docker.io/busybox:1.35" already present on machine
11m         Normal    Created                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Created container: schema-migrator-sync-init
11m         Normal    Started                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Started container schema-migrator-sync-init
9m44s       Normal    Pulled                   pod/signoz-schema-migrator-sync-init-9wrp7                                            Container image "docker.io/clickhouse/clickhouse-server:25.5.6" already present on machine
9m43s       Normal    Created                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Created container: schema-migrator-sync-ch-ready
9m43s       Normal    Started                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Started container schema-migrator-sync-ch-ready
9m36s       Normal    Pulled                   pod/signoz-schema-migrator-sync-init-9wrp7                                            Container image "docker.io/signoz/signoz-schema-migrator:v0.129.6" already present on machine
9m35s       Normal    Created                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Created container: schema-migrator
9m35s       Normal    Started                  pod/signoz-schema-migrator-sync-init-9wrp7                                            Started container schema-migrator
11m         Normal    SuccessfulCreate         job/signoz-schema-migrator-sync-init                                                  Created pod: signoz-schema-migrator-sync-init-9wrp7
6m17s       Normal    Completed                job/signoz-schema-migrator-sync-init                                                  Job completed
11m         Warning   FailedScheduling         pod/signoz-zookeeper-0                                                                0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Warning   FailedScheduling         pod/signoz-zookeeper-0                                                                0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
11m         Normal    Scheduled                pod/signoz-zookeeper-0                                                                Successfully assigned signoz/signoz-zookeeper-0 to work6
11m         Normal    SuccessfulAttachVolume   pod/signoz-zookeeper-0                                                                AttachVolume.Attach succeeded for volume "pvc-302fcf36-8929-452a-abe1-121add70ec8e"
11m         Normal    Pulling                  pod/signoz-zookeeper-0                                                                Pulling image "signoz/zookeeper:3.7.1"
10m         Normal    Pulled                   pod/signoz-zookeeper-0                                                                Successfully pulled image "signoz/zookeeper:3.7.1" in 28.081s (28.081s including waiting). Image size: 273559719 bytes.
10m         Normal    Created                  pod/signoz-zookeeper-0                                                                Created container: zookeeper
10m         Normal    Started                  pod/signoz-zookeeper-0                                                                Started container zookeeper
11m         Normal    SuccessfulCreate         statefulset/signoz-zookeeper                                                          create Claim data-signoz-zookeeper-0 Pod signoz-zookeeper-0 in StatefulSet signoz-zookeeper success
11m         Normal    SuccessfulCreate         statefulset/signoz-zookeeper                                                          create Pod signoz-zookeeper-0 in StatefulSet signoz-zookeeper successful
11m         Normal    IPAllocated              service/signoz                                                                        Assigned IP ["192.168.6.177"]
11m         Warning   deprecatedAnnotation     service/signoz                                                                        Service uses deprecated annotation metallb.universe.tf/loadBalancerIPs
11m         Normal    SuccessfulCreate         statefulset/signoz                                                                    create Claim signoz-db-signoz-0 Pod signoz-0 in StatefulSet signoz success
11m         Normal    SuccessfulCreate         statefulset/signoz                                                                    create Pod signoz-0 in StatefulSet signoz successful

Everything looks normal to me in the logs. The only line that may point to something is

{"timestamp":"2025-10-08T14:39:46.417653421Z","level":"INFO","code":{"function":"github.com/SigNoz/signoz/pkg/factory.(*Registry).Wait","file":"/home/runner/work/signoz/signoz/pkg/factory/registry.go","line":66},"msg":"caught interrupt signal, exiting","pkg":"go.signoz.io/pkg/factory","signal":15}

which is right before a bunch of stopping/stopped/shutting down messages.