You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the generated CLI and operator-facing documentation for the ExpectedMachine interface roles and IP allocation policies added by #3990. Keep this work in a docs-only PR so technical-writing review does not block the code change.
What this involves
Update or regenerate the docs/ CLI reference for role, ip_allocation, fixed_ip, and the optional network_segment_type guard.
Explain Dynamic, Fixed, and Retained behavior for the currently supported Host, DpuOs, and DpuBmc roles.
Explain legacy inference when newer fields are omitted: fixed_ip selects Fixed; otherwise allocation remains Dynamic.
Clarify that fixed addresses select a segment by prefix containment, while DHCP uses the relay or link segment and treats network_segment_type as an optional check.
Keep HostBmc, DPU loopbacks, and the ExpectedInterface rename out of this update until their implementation issues land.
Update the generated CLI and operator-facing documentation for the ExpectedMachine interface roles and IP allocation policies added by #3990. Keep this work in a docs-only PR so technical-writing review does not block the code change.
What this involves
docs/CLI reference forrole,ip_allocation,fixed_ip, and the optionalnetwork_segment_typeguard.Dynamic,Fixed, andRetainedbehavior for the currently supportedHost,DpuOs, andDpuBmcroles.fixed_ipselectsFixed; otherwise allocation remainsDynamic.network_segment_typeas an optional check.HostBmc, DPU loopbacks, and theExpectedInterfacerename out of this update until their implementation issues land.Part of #3491.