Open sunnoy opened 2 weeks ago
pods runing
@sunnoy Thanks! @BruceAko will fix it, refer to https://github.com/dragonflyoss/Dragonfly2/issues/3557.
The Scheduler pod is no longer stated, or active
kubectl get pod -n dragonfly-system -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
dragonfly-dfdaemon-2pdpz 1/1 Running 0 61m 10.244.1.8 kind-worker <none> <none>
dragonfly-dfdaemon-qwhpw 1/1 Running 0 62m 10.244.2.9 kind-worker2 <none> <none>
dragonfly-jaeger-6cb6bb57ff-mwdb9 1/1 Running 1 (4h15m ago) 19h 10.244.2.2 kind-worker2 <none> <none>
dragonfly-manager-59c5cf995c-xcrvq 1/1 Running 0 61m 10.244.1.9 kind-worker <none> <none>
dragonfly-mysql-0 1/1 Running 1 (4h15m ago) 19h 10.244.2.5 kind-worker2 <none> <none>
dragonfly-redis-master-0 1/1 Running 1 (4h15m ago) 19h 10.244.1.5 kind-worker <none> <none>
dragonfly-redis-replicas-0 1/1 Running 1 (4h15m ago) 19h 10.244.1.2 kind-worker <none> <none>
dragonfly-redis-replicas-1 1/1 Running 1 (4h15m ago) 19h 10.244.2.4 kind-worker2 <none> <none>
dragonfly-redis-replicas-2 1/1 Running 1 (4h15m ago) 19h 10.244.1.3 kind-worker <none> <none>
dragonfly-scheduler-0 1/1 Running 0 61m 10.244.1.10 kind-worker <none> <none>
dragonfly-seed-peer-0 1/1 Running 0 61m 10.244.2.10 kind-worker2 <none> <none>
Bug report:
After the deployment is completed as documented, peers are displayed as 0,flow this doc https://d7y.io/docs/getting-started/quick-start/kubernetes/
Expected behavior:
peers not 0
How to reproduce it:
flow this https://d7y.io/docs/getting-started/quick-start/kubernetes/
Environment:
uname -a
): Linux dragonfly-dfdaemon-8lrks 6.8.11-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.8.11-1kali2 (2024-05-30) x86_64 Linux