ClusterD Does Not ConfigMaps
Symptom
ClusterD does not report ConfigMaps during running.
Cause Analysis
The cluster clock may have changed.
Solution
Run the following commands to restart ClusterD. Example command:
kubectl delete -f clusterd-v{version}.yaml
kubectl apply -f clusterd-v{version}.yaml
Parent topic: Faults During Use