Context
When a node has no provider ID yet, getInstance (internal/provider/instances_v2.go) falls back to looking up the Oxide instance by the Kubernetes node name. If the node name doesn't match the Oxide instance name, nodes never initialize — and nothing in the docs or logs tells the user why.
Scope
- Document the requirement in
README.adoc (node name must equal Oxide instance name for bootstrap).
- Small code change in the same PR: when the name lookup returns not-found, wrap the error with a hint that the node name must match the instance name, so the failure is diagnosable from logs.
Done when
The requirement is in the README and the failure mode is diagnosable from CCM logs.
Context
When a node has no provider ID yet,
getInstance(internal/provider/instances_v2.go) falls back to looking up the Oxide instance by the Kubernetes node name. If the node name doesn't match the Oxide instance name, nodes never initialize — and nothing in the docs or logs tells the user why.Scope
README.adoc(node name must equal Oxide instance name for bootstrap).Done when
The requirement is in the README and the failure mode is diagnosable from CCM logs.