Fix check for initialized nodes

[neoaggelos]

Summary

Followup for #564

Changes

• Fix issue where cmdutil.GetNodeStatus() did not properly recognize 503 errors
• Make this part of (k8sd.Client).NodeStatus()
• Adjust CLI to use client.NodeStatus()
• Removed cmdutil.GetNodeStatus() (it is not a command utility, it is functionality we want in the client)

Addresses

$ k8s status
root@t2:~# k8s status
Error: Failed to retrieve the node status.

The error was: failed to GET /k8sd/node: Database is not yet initialized

With the new changes, we are back to the previous error message we had, that shows how to bootstrap a new cluster:

root@t1:~# k8s status
Error: The node is not part of a Kubernetes cluster. You can bootstrap a new cluster with:

  sudo k8s bootstrap

[eaudetcobello]

I notice the isBootstrapped variables have been renamed to initialize. Can you speak a bit on the difference between the two ideas?

[neoaggelos]

I notice the isBootstrapped variables have been renamed to initialize. Can you speak a bit on the difference between the two ideas?

The first node will bootstrap a new cluster. Other nodes join the cluster. isInitialized is used to mean that the node is part of the cluster.

[HomayoonAlimohammadi]

Thanks a lot Angelos! LGTM