...
Confirm that the services have stopped using the kubectl get pod command on the master node. It should show no pods in the default namespace.
After stopping the EdgeX services it is possible to restart them using the edgex_start.yml playbook as usual. Note, however, that the pod names and access tokens will have changed.
Removing Edge Nodes
Stopping Kubernetes
Stopping and Clearing the Docker Registry
Uninstalling Software Components
Removing Configuration and Temporary Data
Troubleshooting
Confirming Node and Service Status
The kubectl command can be used to check the status of most cluster components. kubectl get node will show the health of the master and edge nodes, and kubectl get pod will show the overall status of the EdgeX services. The kubectl describe pod pod-name command can be used to get a more detailed report on the status of a particular pod.
Accessing Logs
Maintenance
Stopping and Restarting EdgeX Services
...
The edge nodes can be removed from the cluster using the following command:
ansible-playbook -i ./hosts delete_from_cluster.yml
This command should be run before stopping the cluster as described in the following section, in order to provide a clean shutdown. It is also possible to re-add the edge nodes using join_cluster.yml, perhaps after editing the configuration in the hosts file.
Stopping Kubernetes
Stopping and Clearing the Docker Registry
Uninstalling Software Components
Removing Configuration and Temporary Data
Troubleshooting
Confirming Node and Service Status
The kubectl command can be used to check the status of most cluster components. kubectl get node will show the health of the master and edge nodes, and kubectl get pod will show the overall status of the EdgeX services. The kubectl describe pod pod-name command can be used to get a more detailed report on the status of a particular pod. The EdgeX configuration UI, described in the section EdgeX Service Configuration UI above, also shows the result of an internal health check of all EdgeX services on the node.
Accessing Logs
The main tool for accessing logs is kubectl logs, run on the master node. This command can be used to show the logs of a running container:
kubectl logs -c container-name pod-name
It can also be used to check the logs of a container which has crashed or stopped:
kubectl logs --previous -c container-name pod-name
And it can be used to stream the logs of a container to a terminal:
kubectl logs -c container-name pod-name -f
The container names can be found in the output of kubectl describe pod or in the edgex/deployments/edgex.yml file (the names of the entries in the containers list).
For the rare cases when the Kubernetes log command does not work, it may be possible to use the docker log command on the node you wish to debug.
Maintenance
Stopping and Restarting EdgeX Services
As described in the Uninstall Guide subsection Stopping EdgeX, the EdgeX services can be stopped and restarted using the edgex_stop.yml and edgex_start.yml playbooks.
Stopping and Restarting the Kubernetes Cluster
Similar to stopping and restarting the EdgeX services, the whole cluster can be stopped and restarted by stopping EdgeX, removing the edge nodes, stopping Kubernetes, starting Kubernetes, adding the edge nodes, and starting EdgeX again:
ansible-playbook -i ./hosts edgex_stop.yml
ansible-playbook -i ./hosts delete_from_cluster.yml
ansible-playbook -i ./hosts reset_cluster.yml --ask-become-pass
ansible-playbook -i ./hosts init_cluster.yml --ask-become-pass
ansible-playbook -i ./hosts join_cluster.yml
ansible-playbook -i ./hosts edgex_start.yml
Adding and Removing Edge Nodes
...