diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 9f47da1dfb5..d5a06efe975 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -7,11 +7,11 @@ on: - "v*" env: - ORIGIN_REPO: smira/talos - ORIGIN_TAG: backports/v1.8.2 - KERNEL_TAG: v1.8.1-6-g7553341 - SBC_TAG: v1.8.1 - RK3588_TAG: v1.8.1-6-gc9d4a5c + ORIGIN_REPO: siderolabs/talos + ORIGIN_TAG: v1.8.2 + KERNEL_TAG: v1.8.2 + SBC_TAG: v1.8.2 + RK3588_TAG: v1.8.2 jobs: talos-build: @@ -82,13 +82,13 @@ jobs: run: | mkdir -p _out # Hack for ARM64 release tool - mv hack/release.sh hack/release.sh.old - curl -sL "https://raw.githubusercontent.com/nberlee/talos/release-1.8-turingrk1/hack/release.sh" -o hack/release.sh - chmod +x hack/release.sh + #mv hack/release.sh hack/release.sh.old + #curl -sL "https://raw.githubusercontent.com/nberlee/talos/release-1.8-turingrk1/hack/release.sh" -o hack/release.sh + #chmod +x hack/release.sh export TAG=${GITHUB_REF#refs/tags/} make release-notes - mv hack/release.sh.old hack/release.sh + #mv hack/release.sh.old hack/release.sh - name: Build an turing-rk1 flashable image run: | diff --git a/website/content/v1.8/talos-guides/install/single-board-computers/turing_rk1.md b/website/content/v1.8/talos-guides/install/single-board-computers/turing_rk1.md index 8d4a60e9790..853735207f4 100644 --- a/website/content/v1.8/talos-guides/install/single-board-computers/turing_rk1.md +++ b/website/content/v1.8/talos-guides/install/single-board-computers/turing_rk1.md @@ -69,10 +69,10 @@ mkdir _out docker pull ghcr.io/nberlee/sbc-turingrk1:v1.8. docker save ghcr.io/nberlee/sbc-turingrk1:v1.8. | tar x --strip-components=1 -C _out -tar xvf _out/sha256/$(ls _out/sha256/ -1Sr | head -1) --strip-components=4 artifacts/arm64/u-boot/turingrk1/u-boot-rockchip-spi.bin +tar xvf _out/sha256/$(ls _out/sha256/ -1S | head -1) --strip-components=4 artifacts/arm64/u-boot/turingrk1/u-boot-rockchip-spi.bin ``` -As the spi-image may be too small for the BMC you may have to flash the raw image first to the eMMC: +As the spi-image does not contain the full GPT tables need have to flash the raw image first to the eMMC, *even if you used Talos on eMMC before*: ``` tpi flash -n -i metal-turing_rk1-arm64.raw ``` @@ -103,7 +103,12 @@ Following the instructions in the uart output to connect to the interactive inst talosctl apply-config --insecure --mode=interactive --nodes ``` -Once the interactive installation is applied, the cluster will form and you can then use `kubectl`. +or use `talosctl gen config` and apply it +```bash +talosctl apply-config --insecure --nodes -f .yaml +``` + +Once the (interactive) installation is applied, the cluster will form and you can then use `kubectl`. ## Retrieve the `kubeconfig`