diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index e9c9f7e138..5377cc7a3a 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -1,6 +1,6 @@ # THIS FILE WAS AUTOMATICALLY GENERATED, PLEASE DO NOT EDIT. # -# Generated on 2024-08-09T09:42:44Z by kres dbf015a. +# Generated on 2024-08-14T14:49:10Z by kres 7be2a05. name: default concurrency: @@ -3180,49 +3180,21 @@ jobs: - name: Generate Checksums run: | cd _out - sha256sum akamai-amd64.raw.gz akamai-arm64.raw.gz aws-amd64.raw.zst aws-arm64.raw.zst azure-amd64.vhd.zst azure-arm64.vhd.zst cloud-images.json digital-ocean-amd64.raw.gz digital-ocean-arm64.raw.gz exoscale-amd64.qcow2.zst exoscale-arm64.qcow2.zst gcp-amd64.raw.tar.gz gcp-arm64.raw.tar.gz hcloud-amd64.raw.zst hcloud-arm64.raw.zst initramfs-amd64.xz initramfs-arm64.xz metal-amd64.iso metal-arm64.iso metal-amd64.raw.zst metal-arm64.raw.zst nocloud-amd64.raw.zst nocloud-arm64.raw.zst opennebula-amd64.raw.zst opennebula-arm64.raw.zst openstack-amd64.raw.zst openstack-arm64.raw.zst oracle-amd64.qcow2.zst oracle-arm64.qcow2.zst scaleway-amd64.raw.zst scaleway-arm64.raw.zst sd-boot-amd64.efi sd-boot-arm64.efi sd-stub-amd64.efi sd-stub-arm64.efi talosctl-cni-bundle-amd64.tar.gz talosctl-cni-bundle-arm64.tar.gz talosctl-darwin-amd64 talosctl-darwin-arm64 talosctl-freebsd-amd64 talosctl-freebsd-arm64 talosctl-linux-amd64 talosctl-linux-arm64 talosctl-linux-armv7 talosctl-windows-amd64.exe upcloud-amd64.raw.zst upcloud-arm64.raw.zst vmware-amd64.ova vmware-arm64.ova vmlinuz-amd64 vmlinuz-arm64 vultr-amd64.raw.zst vultr-arm64.raw.zst > sha256sum.txt - sha512sum akamai-amd64.raw.gz akamai-arm64.raw.gz aws-amd64.raw.zst aws-arm64.raw.zst azure-amd64.vhd.zst azure-arm64.vhd.zst cloud-images.json digital-ocean-amd64.raw.gz digital-ocean-arm64.raw.gz exoscale-amd64.qcow2.zst exoscale-arm64.qcow2.zst gcp-amd64.raw.tar.gz gcp-arm64.raw.tar.gz hcloud-amd64.raw.zst hcloud-arm64.raw.zst initramfs-amd64.xz initramfs-arm64.xz metal-amd64.iso metal-arm64.iso metal-amd64.raw.zst metal-arm64.raw.zst nocloud-amd64.raw.zst nocloud-arm64.raw.zst opennebula-amd64.raw.zst opennebula-arm64.raw.zst openstack-amd64.raw.zst openstack-arm64.raw.zst oracle-amd64.qcow2.zst oracle-arm64.qcow2.zst scaleway-amd64.raw.zst scaleway-arm64.raw.zst sd-boot-amd64.efi sd-boot-arm64.efi sd-stub-amd64.efi sd-stub-arm64.efi talosctl-cni-bundle-amd64.tar.gz talosctl-cni-bundle-arm64.tar.gz talosctl-darwin-amd64 talosctl-darwin-arm64 talosctl-freebsd-amd64 talosctl-freebsd-arm64 talosctl-linux-amd64 talosctl-linux-arm64 talosctl-linux-armv7 talosctl-windows-amd64.exe upcloud-amd64.raw.zst upcloud-arm64.raw.zst vmware-amd64.ova vmware-arm64.ova vmlinuz-amd64 vmlinuz-arm64 vultr-amd64.raw.zst vultr-arm64.raw.zst > sha512sum.txt + sha256sum cloud-images.json initramfs-amd64.xz initramfs-arm64.xz metal-amd64.iso metal-arm64.iso metal-amd64.raw.zst metal-arm64.raw.zst talosctl-cni-bundle-amd64.tar.gz talosctl-cni-bundle-arm64.tar.gz talosctl-darwin-amd64 talosctl-darwin-arm64 talosctl-freebsd-amd64 talosctl-freebsd-arm64 talosctl-linux-amd64 talosctl-linux-arm64 talosctl-linux-armv7 talosctl-windows-amd64.exe vmlinuz-amd64 vmlinuz-arm64 > sha256sum.txt + sha512sum cloud-images.json initramfs-amd64.xz initramfs-arm64.xz metal-amd64.iso metal-arm64.iso metal-amd64.raw.zst metal-arm64.raw.zst talosctl-cni-bundle-amd64.tar.gz talosctl-cni-bundle-arm64.tar.gz talosctl-darwin-amd64 talosctl-darwin-arm64 talosctl-freebsd-amd64 talosctl-freebsd-arm64 talosctl-linux-amd64 talosctl-linux-arm64 talosctl-linux-armv7 talosctl-windows-amd64.exe vmlinuz-amd64 vmlinuz-arm64 > sha512sum.txt - name: release uses: crazy-max/ghaction-github-release@v2 with: body_path: _out/RELEASE_NOTES.md draft: "true" files: |- - _out/akamai-amd64.raw.gz - _out/akamai-arm64.raw.gz - _out/aws-amd64.raw.zst - _out/aws-arm64.raw.zst - _out/azure-amd64.vhd.zst - _out/azure-arm64.vhd.zst _out/cloud-images.json - _out/digital-ocean-amd64.raw.gz - _out/digital-ocean-arm64.raw.gz - _out/exoscale-amd64.qcow2.zst - _out/exoscale-arm64.qcow2.zst - _out/gcp-amd64.raw.tar.gz - _out/gcp-arm64.raw.tar.gz - _out/hcloud-amd64.raw.zst - _out/hcloud-arm64.raw.zst _out/initramfs-amd64.xz _out/initramfs-arm64.xz _out/metal-amd64.iso _out/metal-arm64.iso _out/metal-amd64.raw.zst _out/metal-arm64.raw.zst - _out/nocloud-amd64.raw.zst - _out/nocloud-arm64.raw.zst - _out/opennebula-amd64.raw.zst - _out/opennebula-arm64.raw.zst - _out/openstack-amd64.raw.zst - _out/openstack-arm64.raw.zst - _out/oracle-amd64.qcow2.zst - _out/oracle-arm64.qcow2.zst - _out/scaleway-amd64.raw.zst - _out/scaleway-arm64.raw.zst - _out/sd-boot-amd64.efi - _out/sd-boot-arm64.efi - _out/sd-stub-amd64.efi - _out/sd-stub-arm64.efi _out/talosctl-cni-bundle-amd64.tar.gz _out/talosctl-cni-bundle-arm64.tar.gz _out/talosctl-darwin-amd64 @@ -3233,12 +3205,6 @@ jobs: _out/talosctl-linux-arm64 _out/talosctl-linux-armv7 _out/talosctl-windows-amd64.exe - _out/upcloud-amd64.raw.zst - _out/upcloud-arm64.raw.zst - _out/vmware-amd64.ova - _out/vmware-arm64.ova _out/vmlinuz-amd64 _out/vmlinuz-arm64 - _out/vultr-amd64.raw.zst - _out/vultr-arm64.raw.zst _out/sha*.txt diff --git a/.kres.yaml b/.kres.yaml index f9f30fcc77..854059e2c2 100644 --- a/.kres.yaml +++ b/.kres.yaml @@ -185,41 +185,13 @@ spec: releaseStep: baseDirectory: _out artifacts: - - akamai-amd64.raw.gz - - akamai-arm64.raw.gz - - aws-amd64.raw.zst - - aws-arm64.raw.zst - - azure-amd64.vhd.zst - - azure-arm64.vhd.zst - cloud-images.json - - digital-ocean-amd64.raw.gz - - digital-ocean-arm64.raw.gz - - exoscale-amd64.qcow2.zst - - exoscale-arm64.qcow2.zst - - gcp-amd64.raw.tar.gz - - gcp-arm64.raw.tar.gz - - hcloud-amd64.raw.zst - - hcloud-arm64.raw.zst - initramfs-amd64.xz - initramfs-arm64.xz - metal-amd64.iso - metal-arm64.iso - metal-amd64.raw.zst - metal-arm64.raw.zst - - nocloud-amd64.raw.zst - - nocloud-arm64.raw.zst - - opennebula-amd64.raw.zst - - opennebula-arm64.raw.zst - - openstack-amd64.raw.zst - - openstack-arm64.raw.zst - - oracle-amd64.qcow2.zst - - oracle-arm64.qcow2.zst - - scaleway-amd64.raw.zst - - scaleway-arm64.raw.zst - - sd-boot-amd64.efi - - sd-boot-arm64.efi - - sd-stub-amd64.efi - - sd-stub-arm64.efi - talosctl-cni-bundle-amd64.tar.gz - talosctl-cni-bundle-arm64.tar.gz - talosctl-darwin-amd64 @@ -230,14 +202,8 @@ spec: - talosctl-linux-arm64 - talosctl-linux-armv7 - talosctl-windows-amd64.exe - - upcloud-amd64.raw.zst - - upcloud-arm64.raw.zst - - vmware-amd64.ova - - vmware-arm64.ova - vmlinuz-amd64 - vmlinuz-arm64 - - vultr-amd64.raw.zst - - vultr-arm64.raw.zst generateChecksums: true releaseNotes: RELEASE_NOTES.md - name: e2e-iso diff --git a/hack/release.toml b/hack/release.toml index d3c8580d58..b5711ea58b 100644 --- a/hack/release.toml +++ b/hack/release.toml @@ -12,6 +12,16 @@ previous = "v1.7.0" pre_release = true preface = """\ +Starting with Talos v1.8.0, only standard assets would be published as github release assets. These include: + +* `cloud-images.json` +* `talosctl` binaries +* `kernel` +* `initramfs` +* `metal` iso and disk images +* `talosctl-cni-bundle` + +All other release assets can be downloaded from [Image Factory](https://www.talos.dev/latest/talos-guides/install/boot-assets/#image-factory). """ [notes] diff --git a/website/content/v1.8/advanced/talos-api-access-from-k8s.md b/website/content/v1.8/advanced/talos-api-access-from-k8s.md index c14789e61e..de9fe185b8 100644 --- a/website/content/v1.8/advanced/talos-api-access-from-k8s.md +++ b/website/content/v1.8/advanced/talos-api-access-from-k8s.md @@ -55,7 +55,7 @@ spec: - sh - -c - | - wget -O /usr/local/bin/talosctl https://github.com/siderolabs/talos/releases/download//talosctl-linux-amd64 + wget -O /usr/local/bin/talosctl https://github.com/siderolabs/talos/releases/download/{{< release >}}/talosctl-linux-amd64 chmod +x /usr/local/bin/talosctl while true; talosctl -n 172.20.0.2 version; do sleep 1; done ``` @@ -92,7 +92,7 @@ spec: - sh - -c - | - wget -O /usr/local/bin/talosctl https://github.com/siderolabs/talos/releases/download//talosctl-linux-amd64 + wget -O /usr/local/bin/talosctl https://github.com/siderolabs/talos/releases/download/{{< release >}}/talosctl-linux-amd64 chmod +x /usr/local/bin/talosctl while true; talosctl -n 172.20.0.2 version; do sleep 1; done image: alpine:3 diff --git a/website/content/v1.8/talos-guides/install/bare-metal-platforms/digital-rebar.md b/website/content/v1.8/talos-guides/install/bare-metal-platforms/digital-rebar.md deleted file mode 100644 index 84c389a03e..0000000000 --- a/website/content/v1.8/talos-guides/install/bare-metal-platforms/digital-rebar.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -title: "Digital Rebar" -description: "In this guide we will create an Kubernetes cluster with 1 worker node, and 2 controlplane nodes using an existing digital rebar deployment." -aliases: - - ../../../bare-metal-platforms/digital-rebar ---- - -## Prerequisites - -- 3 nodes (please see [hardware requirements]({{< relref "../../../introduction/system-requirements/" >}})) -- Loadbalancer -- Digital Rebar Server -- Talosctl access (see [talosctl setup]({{< relref "../../../introduction/getting-started/#talosctl" >}})) - -## Creating a Cluster - -In this guide we will create an Kubernetes cluster with 1 worker node, and 2 controlplane nodes. -We assume an existing digital rebar deployment, and some familiarity with iPXE. - -We leave it up to the user to decide if they would like to use static networking, or DHCP. -The setup and configuration of DHCP will not be covered. - -### Create the Machine Configuration Files - -#### Generating Base Configurations - -Using the DNS name of the load balancer, generate the base configuration files for the Talos machines: - -```bash -$ talosctl gen config talos-k8s-metal-tutorial https://: -created controlplane.yaml -created worker.yaml -created talosconfig -``` - -> The loadbalancer is used to distribute the load across multiple controlplane nodes. -> This isn't covered in detail, because we assume some loadbalancing knowledge before hand. -> If you think this should be added to the docs, please [create a issue](https://github.com/siderolabs/talos/issues). - -At this point, you can modify the generated configs to your liking. -Optionally, you can specify `--config-patch` with RFC6902 jsonpatch which will be applied during the config generation. - -#### Validate the Configuration Files - -```bash -$ talosctl validate --config controlplane.yaml --mode metal -controlplane.yaml is valid for metal mode -$ talosctl validate --config worker.yaml --mode metal -worker.yaml is valid for metal mode -``` - -#### Publishing the Machine Configuration Files - -Digital Rebar has a built-in fileserver, which means we can use this feature to expose the talos configuration files. -We will place `controlplane.yaml`, and `worker.yaml` into Digital Rebar file server by using the `drpcli` tools. - -Copy the generated files from the step above into your Digital Rebar installation. - -```bash -drpcli file upload .yaml as .yaml -``` - -Replacing `` with controlplane or worker. - -### Download the boot files - -Download a recent version of `boot.tar.gz` from [github.](https://github.com/siderolabs/talos/releases/) - -Upload to DRB: - -```bash -$ drpcli isos upload boot.tar.gz as talos.tar.gz -{ - "Path": "talos.tar.gz", - "Size": 96470072 -} -``` - -We have some Digital Rebar [example files](https://github.com/siderolabs/talos/tree/master/hack/test/digitalrebar/) in the Git repo you can use to provision Digital Rebar with drpcli. - -To apply these configs you need to create them, and then apply them as follow: - -```bash -$ drpcli bootenvs create talos -{ - "Available": true, - "BootParams": "", - "Bundle": "", - "Description": "", - "Documentation": "", - "Endpoint": "", - "Errors": [], - "Initrds": [], - "Kernel": "", - "Meta": {}, - "Name": "talos", - "OS": { - "Codename": "", - "Family": "", - "IsoFile": "", - "IsoSha256": "", - "IsoUrl": "", - "Name": "", - "SupportedArchitectures": {}, - "Version": "" - }, - "OnlyUnknown": false, - "OptionalParams": [], - "ReadOnly": false, - "RequiredParams": [], - "Templates": [], - "Validated": true -} -``` - -```bash -drpcli bootenvs update talos - < bootenv.yaml -``` - -> You need to do this for all files in the example directory. -> If you don't have access to the `drpcli` tools you can also use the webinterface. - -It's important to have a corresponding SHA256 hash matching the boot.tar.gz - -#### Bootenv BootParams - -We're using some of Digital Rebar built in templating to make sure the machine gets the correct role assigned. - -`talos.platform=metal talos.config={{ .ProvisionerURL }}/files/{{.Param \"talos/role\"}}.yaml"` - -This is why we also include a `params.yaml` in the example directory to make sure the role is set to one of the following: - -- controlplane -- worker - -The `{{.Param \"talos/role\"}}` then gets populated with one of the above roles. - -### Boot the Machines - -In the UI of Digital Rebar you need to select the machines you want to provision. -Once selected, you need to assign to following: - -- Profile -- Workflow - -This will provision the Stage and Bootenv with the talos values. -Once this is done, you can boot the machine. - -### Bootstrap Etcd - -To configure `talosctl` we will need the first control plane node's IP: - -Set the `endpoints` and `nodes`: - -```bash -talosctl --talosconfig talosconfig config endpoint -talosctl --talosconfig talosconfig config node -``` - -Bootstrap `etcd`: - -```bash -talosctl --talosconfig talosconfig bootstrap -``` - -### Retrieve the `kubeconfig` - -At this point we can retrieve the admin `kubeconfig` by running: - -```bash -talosctl --talosconfig talosconfig kubeconfig . -``` diff --git a/website/content/v1.8/talos-guides/install/bare-metal-platforms/pxe.md b/website/content/v1.8/talos-guides/install/bare-metal-platforms/pxe.md index 271e855e87..55990504ba 100644 --- a/website/content/v1.8/talos-guides/install/bare-metal-platforms/pxe.md +++ b/website/content/v1.8/talos-guides/install/bare-metal-platforms/pxe.md @@ -4,7 +4,7 @@ description: "Booting Talos over the network on bare-metal with PXE." --- Talos can be installed on bare-metal using PXE service. -There are two more detailed guides for PXE booting using [Matchbox]({{< relref "matchbox">}}) and [Digital Rebar]({{< relref "digital-rebar">}}). +There are more detailed guides for PXE booting using [Matchbox]({{< relref "matchbox">}}). This guide describes generic steps for PXE booting Talos on bare-metal. diff --git a/website/content/v1.8/talos-guides/install/boot-assets.md b/website/content/v1.8/talos-guides/install/boot-assets.md index bf58446f2e..e0a88bfe2d 100644 --- a/website/content/v1.8/talos-guides/install/boot-assets.md +++ b/website/content/v1.8/talos-guides/install/boot-assets.md @@ -3,7 +3,7 @@ title: "Boot Assets" description: "Creating customized Talos boot assets, disk images, ISO and installer images." --- -Talos Linux provides a set of pre-built images on the [release page](https://github.com/siderolabs/talos/releases/{{< release >}}), but these images +Talos Linux provides boot images via [Image Factory](#image-factory), but these images can be customized further for a specific use case: * adding [system extensions]({{< relref "../configuration/system-extensions" >}}) diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/akamai.md b/website/content/v1.8/talos-guides/install/cloud-platforms/akamai.md index a3384c6c3b..3a7fcd44d2 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/akamai.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/akamai.md @@ -16,7 +16,7 @@ Make sure to follow [installation](https://www.linode.com/docs/products/tools/cl ### Upload image -Download the Akamai image `akamai-amd64.raw.gz` from the [latest Talos release](https://github.com/siderolabs/talos/releases/latest/). +Download the Akamai image `akamai-amd64.raw.gz` from [Image Factory](https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/akamai-amd64.raw.gz). Upload the image diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/aws.md b/website/content/v1.8/talos-guides/install/cloud-platforms/aws.md index 35b1daaa7e..1ffd1b6c14 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/aws.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/aws.md @@ -129,10 +129,10 @@ Note that the role should be associated with the S3 bucket we created above. #### Create the Image Snapshot -First, download the AWS image from a Talos release: +First, download the AWS image from Image Factory: ```bash -curl -L https://github.com/siderolabs/talos/releases/download/{{< release >}}/aws-amd64.raw.xz | xz -d > disk.raw +curl -L https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/aws-amd64.raw.xz | xz -d > disk.raw ``` Copy the RAW disk to S3 and import it as a snapshot: diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/digitalocean.md b/website/content/v1.8/talos-guides/install/cloud-platforms/digitalocean.md index 5a15dd3f04..516af37a38 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/digitalocean.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/digitalocean.md @@ -1,7 +1,7 @@ --- title: "DigitalOcean" description: "Creating a cluster via the CLI on DigitalOcean." -aliases: +aliases: - ../../../cloud-platforms/digitalocean --- @@ -13,7 +13,7 @@ If you need more information on DigitalOcean specifics, please see the [official ### Create the Image -Download the DigitalOcean image `digital-ocean-amd64.raw.gz` from the [latest Talos release](https://github.com/siderolabs/talos/releases/latest/). +Download the DigitalOcean image `digital-ocean-amd64.raw.gz` from the [Image Factory](https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/digital-ocean-amd64.raw.gz). >Note: the minimum version of Talos required to support Digital Ocean is v1.3.3. diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/gcp/talos-ha.jinja b/website/content/v1.8/talos-guides/install/cloud-platforms/gcp/talos-ha.jinja index afd1fba081..c6530e1804 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/gcp/talos-ha.jinja +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/gcp/talos-ha.jinja @@ -11,7 +11,7 @@ resources: - name: gcr.io/cloud-builders/curl args: - -fSLO - - https://github.com/siderolabs/talos/releases/download/{{ properties["talosVersion"] }}/gcp-amd64.tar.gz + - https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{ properties["talosVersion"] }}/gcp-amd64.raw.tar.gz - name: gcr.io/cloud-builders/gsutil args: - -m diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/hetzner.md b/website/content/v1.8/talos-guides/install/cloud-platforms/hetzner.md index ceecada597..97bd2040d4 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/hetzner.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/hetzner.md @@ -37,7 +37,7 @@ df # Download the Talos image cd /tmp -wget -O /tmp/talos.raw.xz https://github.com/siderolabs/talos/releases/download/{{< release >}}/hcloud-amd64.raw.xz +wget -O /tmp/talos.raw.xz https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/hcloud-amd64.raw.xz # Replace system xz -d -c /tmp/talos.raw.xz | dd of=/dev/sda && sync # shutdown the instance @@ -87,7 +87,7 @@ variable "server_location" { } locals { - image = "https://github.com/siderolabs/talos/releases/download/${var.talos_version}/hcloud-${var.arch}.raw.xz" + image = "https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/${var.talos_version}/hcloud-${var.arch}.raw.xz" } source "hcloud" "talos" { diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/upcloud.md b/website/content/v1.8/talos-guides/install/cloud-platforms/upcloud.md index 812b4228e6..2d9e11bdfa 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/upcloud.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/upcloud.md @@ -64,7 +64,7 @@ variable "talos_version" { } locals { - image = "https://github.com/siderolabs/talos/releases/download/${var.talos_version}/upcloud-amd64.raw.xz" + image = "https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/${var.talos_version}/upcloud-amd64.raw.xz" } variable "username" { diff --git a/website/content/v1.8/talos-guides/install/cloud-platforms/vultr.md b/website/content/v1.8/talos-guides/install/cloud-platforms/vultr.md index 6a947c94bd..e09e2fbb0e 100644 --- a/website/content/v1.8/talos-guides/install/cloud-platforms/vultr.md +++ b/website/content/v1.8/talos-guides/install/cloud-platforms/vultr.md @@ -19,16 +19,18 @@ Make sure to follow installation and authentication instructions for the `vultr- First step is to make the Talos ISO available to Vultr by uploading the latest release of the ISO to the Vultr ISO server. ```bash -vultr-cli iso create --url https://github.com/siderolabs/talos/releases/download/{{< release >}}/metal-amd64.iso +vultr-cli iso create --url https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}vultr-amd64.iso ``` -Make a note of the `ID` in the output, it will be needed later when creating the instances. +Make a note of the `ID` in the output, it will be needed later when creating the instances.met #### PXE Booting via Image Factory Talos Linux can be PXE-booted on Vultr using [Image Factory]({{< relref "../../../learn-more/image-factory" >}}), using the `vultr` platform: e.g. `https://pxe.factory.talos.dev/pxe/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/vultr-amd64` (this URL references the default schematic and `amd64` architecture). +Make a note of the `ID` in the output, it will be needed later when creating the instances. + ### Create a Load Balancer A load balancer is needed to serve as the Kubernetes endpoint for the cluster. diff --git a/website/content/v1.8/talos-guides/install/local-platforms/virtualbox.md b/website/content/v1.8/talos-guides/install/local-platforms/virtualbox.md index 5874a699b6..62c3b61d04 100644 --- a/website/content/v1.8/talos-guides/install/local-platforms/virtualbox.md +++ b/website/content/v1.8/talos-guides/install/local-platforms/virtualbox.md @@ -36,20 +36,18 @@ For manually installation and other platform please see the [talosctl installati ### Download ISO Image -Download the ISO image from the Talos release page. -You can download `metal-amd64.iso` via -[github.com/siderolabs/talos/releases](https://github.com/siderolabs/talos/releases) +Download the ISO image from [Image Factory](https://www.talos.dev/latest/talos-guides/install/boot-assets/#image-factory). ```bash mkdir -p _out/ -curl https://github.com/siderolabs/talos/releases/download//metal-.iso -L -o _out/metal-.iso +curl https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba//metal-.iso -L -o _out/metal-.iso ``` For example version `{{< release >}}` for `linux` platform: ```bash mkdir -p _out/ -curl https://github.com/siderolabs/talos/releases/download/{{< release >}}/metal-amd64.iso -L -o _out/metal-amd64.iso +curl https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/metal-amd64.iso -L -o _out/metal-amd64.iso ``` ## Create VMs diff --git a/website/content/v1.8/talos-guides/install/virtualized-platforms/proxmox.md b/website/content/v1.8/talos-guides/install/virtualized-platforms/proxmox.md index 86a6f2b344..2c6cf2eaf0 100644 --- a/website/content/v1.8/talos-guides/install/virtualized-platforms/proxmox.md +++ b/website/content/v1.8/talos-guides/install/virtualized-platforms/proxmox.md @@ -32,20 +32,18 @@ For manually installation and other platform please see the [talosctl installati ### Download ISO Image -In order to install Talos in Proxmox, you will need the ISO image from the Talos release page. -You can download `metal-amd64.iso` via -[github.com/siderolabs/talos/releases](https://github.com/siderolabs/talos/releases) +In order to install Talos in Proxmox, you will need the ISO image from [Image Factory](https://www.talos.dev/latest/talos-guides/install/boot-assets/#image-factory).. ```bash mkdir -p _out/ -curl https://github.com/siderolabs/talos/releases/download/{{< release >}}/metal-.iso -L -o _out/metal-.iso +curl https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba//metal-.iso -L -o _out/metal-.iso ``` For example version `{{< release >}}` for `linux` platform: ```bash mkdir -p _out/ -curl https://github.com/siderolabs/talos/releases/download/{{< release >}}/metal-amd64.iso -L -o _out/metal-amd64.iso +curl https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/metal-amd64.iso -L -o _out/metal-amd64.iso ``` ### QEMU guest agent support (iso) diff --git a/website/content/v1.8/talos-guides/install/virtualized-platforms/vagrant-libvirt.md b/website/content/v1.8/talos-guides/install/virtualized-platforms/vagrant-libvirt.md index 389e8242e5..d414b2e5f2 100644 --- a/website/content/v1.8/talos-guides/install/virtualized-platforms/vagrant-libvirt.md +++ b/website/content/v1.8/talos-guides/install/virtualized-platforms/vagrant-libvirt.md @@ -26,7 +26,7 @@ We will also configure a virtual IP address on Talos to achieve high-availabilit First, we download the latest `metal-amd64.iso` ISO from GitHub releases into the `/tmp` directory. ```bash -wget --timestamping https://github.com/siderolabs/talos/releases/download/{{< release >}}/metal-amd64.iso -O /tmp/metal-amd64.iso +wget --timestamping curl https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/{{< release >}}/metal-amd64.iso -O /tmp/metal-amd64.iso ``` Create a `Vagrantfile` with the following contents: diff --git a/website/content/v1.8/talos-guides/install/virtualized-platforms/vmware.md b/website/content/v1.8/talos-guides/install/virtualized-platforms/vmware.md index 94840d75ed..2bcddc09fe 100644 --- a/website/content/v1.8/talos-guides/install/virtualized-platforms/vmware.md +++ b/website/content/v1.8/talos-guides/install/virtualized-platforms/vmware.md @@ -118,12 +118,14 @@ You may now skip past the "Manual Approach" section down to "Bootstrap Cluster". #### Import the OVA into vCenter -A `talos.ova` asset is published with each [release](https://github.com/siderolabs/talos/releases). +A `talos.ova` asset is available from [Image Factory](https://www.talos.dev/latest/talos-guides/install/boot-assets/#image-factory). We will refer to the version of the release as `$TALOS_VERSION` below. It can be easily exported with `export TALOS_VERSION="v0.3.0-alpha.10"` or similar. +The download link already includes the `talos-vmtoolsd` extension. + ```bash -curl -LO https://github.com/siderolabs/talos/releases/download/$TALOS_VERSION/talos.ova +curl -LO https://factory.talos.dev/image/903b2da78f99adef03cbbd4df6714563823f63218508800751560d3bc3557e40/${TALOS_VERSION}/vmware-amd64.ova ``` Create a content library (if needed) with: