Support HTTPBoot Enablement Using MetalAPI

Summary

This issue focuses on finalizing the reliable enablement of HTTPBoot as a mainstream boot mechanism across Ironcore. While initial support is in place, we aim to operationalize HTTPBoot for all relevant machines using MetalAPI and Metal Operator components.

Scope

✅ In Scope

• Enforce HTTPBoot across all servers using Metal Operator and BIOSSettings API
• Ensure FeDHCP and ignition flows reliably support HTTPBoot

❌ Out of Scope

• SecureBoot compatibility validation (tracked separately)
• Internal Harbor registry migration (to be discussed)

Responsible Areas

• Metal Automation

Contributors

• @5kt
• @damyan
• @hardikdr

Acceptance Criteria

• Metal Automation

  • HTTPBoot can be reliably enforced using BIOSSettings API
  • HTTPBoot is enabled across all test landscape computes
  • FeDHCP and Metal Operator reliably serve the correct boot flow
  • Clear documentation covering how HTTPBoot works end-to-end in Ironcore

Action Items

• Assign labels (e.g., kind/epic, area/metal-automation, area/operatingsystem)
• Set milestone (H2/2025)
• Create sub-issues for BIOSSettings enforcement and DNS resolution
• Assign an owner
• Add to ironcore-dev/roadmap project board

Start with the Metal Automation scope and review the BIOSSettings API, Metal Operator, FeDHCP, and ignition flows together. Break the epic into the planned BIOSSettings enforcement and DNS-resolution sub-issues before changing anything. Done means HTTPBoot is enforced across the test landscape, the boot flow is reliable, and end-to-end Ironcore documentation is available.