Troubleshoot
Read the fleet first:
kubectl --context YOUR_CONTEXT -n fleets describe celldfleet my-fleetkubectl --context YOUR_CONTEXT -n fleets get celldfleet my-fleet -o yaml| Symptom | Next step |
|---|---|
| Operator unavailable, missing CRD or namespace access | Installation. |
| Pod Pending, claim unbound or newcomer unready | Scheduling and storage. |
| Runtime not ready, waiting for a retained peer, a lost node or a lost disk | Runtime recovery. |
| A rollout or scale-in that keeps waiting, a member waiting to be replaced, or a blocked deletion | Waiting and blocked changes. |
| Incomplete or ineffective capacity observations | Capacity policy. |
Ready describes availability. It does not mean celld has finished recovering
every session.
Use the conditions reference to interpret the type, reason and message together. Preserve storage whenever a disk’s contents are uncertain.
Experimental software for evaluation.Capabilities and limitations· Contribute