From e62c91e92862fab80c441d9c473c7f03eb581db2 Mon Sep 17 00:00:00 2001 From: Niko Date: Fri, 5 Jun 2026 22:28:46 -0700 Subject: [PATCH 1/3] Clarify IGNITION_CONFIG as optional in documentation Added a comment to clarify that IGNITION_CONFIG is optional. --- modules/ROOT/pages/provisioning-hetzner.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/provisioning-hetzner.adoc b/modules/ROOT/pages/provisioning-hetzner.adoc index 6f291e32..f6ae06a3 100644 --- a/modules/ROOT/pages/provisioning-hetzner.adoc +++ b/modules/ROOT/pages/provisioning-hetzner.adoc @@ -94,7 +94,7 @@ SSH_KEY_NAME="fedora-coreos-hetzner" # See: hcloud ssh-key list DATACENTER="fsn1-dc14" # See: hcloud datacenter list TYPE="cx22" # See: hcloud server-type list NAME="fedora-coreos-test" -IGNITION_CONFIG="./config.ign" +IGNITION_CONFIG="./config.ign" # optional, see prerequisites. hcloud server create \ --name "$NAME" \ --type "$TYPE" \ From 29cb69a91a100a39bb88d55e1715a8e76e4d25ce Mon Sep 17 00:00:00 2001 From: Niko Date: Sun, 7 Jun 2026 16:06:38 -0700 Subject: [PATCH 2/3] make clear that hetzner servers can be created from snapshots in the web UI --- modules/ROOT/pages/provisioning-hetzner.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/provisioning-hetzner.adoc b/modules/ROOT/pages/provisioning-hetzner.adoc index f6ae06a3..b6010007 100644 --- a/modules/ROOT/pages/provisioning-hetzner.adoc +++ b/modules/ROOT/pages/provisioning-hetzner.adoc @@ -45,7 +45,7 @@ Verify the download, following the instructions on that page. + [source, bash] ---- -IMAGE_NAME="fedora-coreos-41.20250213.0-hetzner.x86_64.raw.xz" +IMAGE_NAME="" export HCLOUD_TOKEN="" STREAM="stable" # or "testing", "next" HETZNER_ARCH="x86" # or "arm" @@ -79,8 +79,7 @@ SSH_KEY_NAME="fedora-coreos-hetzner" hcloud ssh-key create --name "$SSH_KEY_NAME" --public-key "$SSH_PUBKEY" ---- + -. Launch a server. Your Ignition configuration can be passed to the VM as its user data, or you can skip passing user data if you just want SSH access. - This provides an easy way to test out FCOS without first creating an Ignition config. +. Launch a server. You can create a server from the snapshot created in the previous in the web console and skip passing user data if you just want SSH access. This provides an easy way to test out FCOS without first creating an Ignition config. To use an Ignition configuration, pass it to the VM as user data as below. + .Example launching FCOS on Hetzner using an Ignition configuration file and SSH key [source, bash] From 9e6169b2d07e82bada0f386350f7db1b0f9091f4 Mon Sep 17 00:00:00 2001 From: Niko Date: Sun, 7 Jun 2026 16:10:19 -0700 Subject: [PATCH 3/3] typo --- modules/ROOT/pages/provisioning-hetzner.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/provisioning-hetzner.adoc b/modules/ROOT/pages/provisioning-hetzner.adoc index b6010007..d2657d61 100644 --- a/modules/ROOT/pages/provisioning-hetzner.adoc +++ b/modules/ROOT/pages/provisioning-hetzner.adoc @@ -79,7 +79,7 @@ SSH_KEY_NAME="fedora-coreos-hetzner" hcloud ssh-key create --name "$SSH_KEY_NAME" --public-key "$SSH_PUBKEY" ---- + -. Launch a server. You can create a server from the snapshot created in the previous in the web console and skip passing user data if you just want SSH access. This provides an easy way to test out FCOS without first creating an Ignition config. To use an Ignition configuration, pass it to the VM as user data as below. +. Launch a server. You can create a server in the web console from the snapshot we just created and skip passing an Ignition file if you just want SSH access. This provides an easy way to test out FCOS without first creating an Ignition config. To use an Ignition configuration, pass it to the VM as user data as below. + .Example launching FCOS on Hetzner using an Ignition configuration file and SSH key [source, bash]