Implement new platform Hetzner

[dustymabe]

Implementing a new supported platform

During Development

Create PRs addressing the following:

• Ignition providers/hetzner: add support for Hetzner Cloud ignition#1707
  • Add userdata fetch
  • If the platform supports it (unlikely), add userdata deletion
• Afterburn providers/hetzner: add support for Hetzner Cloud afterburn#996
  • (Cloud Only) Add relevant attributes
  • (Cloud Only) Add SSH key support if available
  • (Cloud Only) Add hostname support if available
  • (Cloud Only) Add check-in if needed (unlikely)
• stream-metadata-go Add Hetzner artifact to stream and release metadata stream-metadata-go#79
  • Add platform to the Media struct in release/release.go
  • Add supporting code for new platform to toStreamArch func in release/translate.go
  • (Cloud Only) Cloud Images need to have an Images field
• (Cloud Only) stream-metadata-rust (example PR)
• fedora-coreos-tracker metadata: add examples for hetzner #1875
  • Update the metadata for the new platform
• coreos-assembler support building hetzner disk images coreos-assembler#4023
  • Implement required functionality to support new platform
• fedora-coreos-config Not needed according to Implement new platform Hetzner #1874 (comment)
  • Add a stanza to platforms.yaml if the system should use a serial console, or both serial and graphical consoles
• fedora-websites-3.0
  • Add friendly name for platform to components/utilities/FpDownloadItem.vue
    • https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/commit/358ffb00a9561b7335de7d4c1972cea01a834531
  • Add artifact to pages/coreos/download.vue
    • https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/commit/358ffb00a9561b7335de7d4c1972cea01a834531
  • Possibly add logo to content/editions/coreos/home.yml
    • https://gitlab.com/fedora/websites-apps/fedora-websites/cms/fedoraproject.org/-/commit/690a054009d2f02a29592169a114fe38e4d54cb6
• fedora-coreos-browser browser: add Hetzner/ProxmoxVE fedora-coreos-browser#52
  • Add a list element for new platform in browser/index.html
• build pipeline config: add hetzner for x86_64 and aarch64 fedora-coreos-pipeline#1110
  • Add platform to the list found in config.yaml for building the new artifact
• fedora-coreos-docs Provisioning: Add Hetzner fedora-coreos-docs#654
  • Add a provisioning-<platform>.adoc that walks through how to setup the new platform
  • Add an entry in the modules/ROOT/nav.adoc that points to new documentation

At Release

1. Merge upstream changes and put out a release:
   • Ignition
   • Afterburn
2. Merge metadata changes:
   • stream-metadata-go
   • stream-metadata-rust
   • fedora-coreos-tracker
   • fedora website
   • fedora-coreos-browser
3. Release updated components
   • Create and follow release checklist for stream-metadata-go
   • Ensure that Dependabot has PRed stream-metadata-go into fedora-coreos-stream-generator and coreos-assembler. Merge the update PRs.
     • This can be triggered manually by navigating to fedora-coreos-stream-generator's Dependabot and coreos-assembler's Dependabot respectively, then clicking "Check for updates".
       • This might need to be done a few times, as Dependabot might not pick up tag changes for a few attempts after initial tagging.
   • Create and follow release checklist for fedora-coreos-stream-generator
4. Merge the following changes:
   • coreos-assembler
5. Wait for updates made to coreos-assembler to be propagated to latest container
   • Download latest version of coreos-assembler container. Verify platform support functionality.
6. Merge changes for:
   • Build pipeline
7. Wait for new images to reach stable then merge documentation.
   • fedora-coreos-docs merged

[dustymabe]

• providers/hetzner: add support for Hetzner Cloud ignition#1707
• providers/hetzner: add support for Hetzner Cloud afterburn#996
• metadata: add examples for hetzner #1875

[dustymabe]

• support building hetzner disk images coreos-assembler#4023

[dustymabe]

Add a stanza to platforms.yaml if the system should use a serial console, or both serial and graphical consoles

@travier mind helping me to know if this is needed?

[travier]

Add a stanza to platforms.yaml if the system should use a serial console, or both serial and graphical consoles

I'll check again when testing the image.

[travier]

Add a stanza to platforms.yaml if the system should use a serial console, or both serial and graphical consoles

I'll check again when testing the image.

When testing this, I immediately got console output on boot with the online console access. So I would say that we don't need to do anything more.

[travier]

I've also verified that both Ingnition and Afterburn appears to be working as expected.

[travier]

I've updated the docs at coreos/fedora-coreos-docs#654 to use those upcoming images.

[dustymabe]

• Add Hetzner artifact to stream and release metadata stream-metadata-go#79

[dustymabe]

websites changes:

• https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/commit/358ffb00a9561b7335de7d4c1972cea01a834531
• https://gitlab.com/fedora/websites-apps/fedora-websites/cms/fedoraproject.org/-/commit/690a054009d2f02a29592169a114fe38e4d54cb6