Context
The Zones() doc comment in internal/provider/provider.go says "Zone and region information is retrieved from InstanceMetadata instead" — but InstanceMetadata (internal/provider/instances_v2.go) never populates Zone or Region. Result: nodes get no topology.kubernetes.io/region or topology.kubernetes.io/zone labels, and the docs contradict the behavior.
Scope
Decide and implement one of:
- Populate
Region (silo name is a reasonable stand-in until Oxide has multi-rack topology), optionally Zone.
- Fix the
Zones() comment to say topology is intentionally unset and why.
Record the decision in this issue.
Done when
Docs and behavior agree, with the decision recorded.
Context
The
Zones()doc comment ininternal/provider/provider.gosays "Zone and region information is retrieved fromInstanceMetadatainstead" — butInstanceMetadata(internal/provider/instances_v2.go) never populatesZoneorRegion. Result: nodes get notopology.kubernetes.io/regionortopology.kubernetes.io/zonelabels, and the docs contradict the behavior.Scope
Decide and implement one of:
Region(silo name is a reasonable stand-in until Oxide has multi-rack topology), optionallyZone.Zones()comment to say topology is intentionally unset and why.Record the decision in this issue.
Done when
Docs and behavior agree, with the decision recorded.