CCM unable to get node info

[deitch]

When running, it complains about getting node info.

In k3s:

I1112 14:43:00.227384       1 controllermanager.go:244] Started "cloud-node-lifecycle"
E1112 14:43:00.239786       1 node_controller.go:140] provider name from providerID should be packet: k3s://ccm01
E1112 14:43:00.983278       1 node_controller.go:140] provider name from providerID should be packet: k3s://ccm02

In k8s:

I1112 15:17:52.834928       1 controllermanager.go:244] Started "cloud-node-lifecycle"
E1112 15:17:53.263606       1 node_controller.go:140] unexpected providerID format: ef6660bc-6578-490c-9d49-3ddadb2c483e, format should be: packet://device-id
E1112 15:17:54.178116       1 node_controller.go:140] unexpected providerID format: e197e6a0-4a2b-4256-9b7a-c1ea510579d4, format should be: packet://device-id

In all cases, it appears it doesn't send anything consistent.

[deitch]

Defer on fixing these until #26 is in at least

[deitch]

The k3s one appears to be a k3s bug, see this issue

The k8s one might be that we need to return the entire URI as packet://<id> instead of just <id> from InstanceID(). Still checking.

[deitch]

Nope, we are doing the right thing for InstanceID(). So it isn't that. The error message is being returned from here

[deitch]

The k3s issue is not a bug, but rather missing documentation on, "how to run k3s with an external CCM". It is being addressed in the referenced k3s issue.

[deitch]

The k8s one also is not an issue. If you start the node kubelet without --cloud-provider=external, the node cannot get it again. You need to clear it completely via:

• stop the kubelet, e.g. systemctl stop kubelet (adjust to your system)
• delete the node kubectl delete node <name>
• add the --cloud-provider=external flag to the kubelet parameters
• start the kubelet, e.g. systemctl start kubelet (adjust to your system)