IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Uses Sidero Labs d2ctl to install a small sample of
common cluster services to ensure the Talos cluster
is capable.
Signed-off-by: Tim Jones <tim.jones@siderolabs.com>
Fixes#5080
This updates all package dependencies to 1.0 versions.
Add a GPL note to README.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Ref: https://github.com/talos-systems/pkgs/pull/394
Kernel size also reduced by 1Meg
Before:
```bash
❯ du -sh _out/vmlinuz-amd64
16M _out/vmlinuz-amd64
❯ file _out/vmlinuz-amd64
_out/vmlinuz-amd64: Linux kernel x86 boot executable bzImage, version 5.15.22-talos (@buildkitsandbox) #1 SMP Wed Feb 9 19:19:47 UTC 2022, RO-rootFS, swap_dev 0xF, Normal VGA
❯ du -sh _out/vmlinuz-arm64
57M _out/vmlinuz-arm64
```
After:
```bash
❯ du -sh _out/vmlinuz-amd64
15M _out/vmlinuz-amd64
❯ file _out/vmlinuz-amd64
_out/vmlinuz-amd64: Linux kernel x86 boot executable bzImage, version 5.15.22-talos (@buildkitsandbox) #1 SMP Thu Feb 10 18:20:11 UTC 2022, RO-rootFS, swap_dev 0xE, Normal VGA
❯ du -sh _out/vmlinuz-arm64
56M _out/vmlinuz-arm64
```
Signed-off-by: Noel Georgi <git@frezbo.dev>
Version was never passed properly, plus the goreleaser is deprecated
now, switch to golangci-lint equivalent script.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Containerd doesn't support merging plugin configuration from multiple
sources, and Talos has several pieces which configure CRI plugin:
(see https://github.com/containerd/containerd/issues/5837)
* base config
* registry mirror config
* system extensions
* ...
So we implement our own simple way of merging config parts (by simply
concatenating text files) to build a final `cri.toml`.
At the same time containerd migrated to a new format to specify registry
mirror configuration, while old way (via CRI config) is going to be
removed in 1.7.0. New way also allows to apply most of registry
configuration (except for auth) on the fly.
Also, containerd was updated to 1.6.0-rc.0 and runc to 1.1.0.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This will be required to preserve platform network configuration in a
cache across boots. Network configuration will be marshaled to YAML and
unmarshaled back.
Changes are pretty simple and most of the code is auto-generated:
replace `stringer` codegen with `enumer` which produces also methods
which convert from string back to enum values.
Added tests to verify YAML marshaling/unmarshaling.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Fixes kexec on RPI4
Since BL31 is now enabled `talosctl shutdown` puts the Pi in a low power state instead of rebooting
Ref: https://github.com/talos-systems/pkgs/pull/375
Signed-off-by: Noel Georgi <git@frezbo.dev>
Instead, build all images for a release and in the integration pipeline
which is triggered `nightly` and can be promoted to with
`/promote integration-images`.
This saves time and resources on regular builds.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
In preparation for beta release, use final released versions.
There should be no actual package updates, just bumped versions.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Update Go modules to the latest versions including talos-systems/
released modules.
In preparation for 0.14-beta release.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
The `installer` image is used for initial install and upgrades, so it
contains only Talos artifacts for the same arch as the image
The `imager` image is used to produce Talos images, so it contains artifacts
for all arhitectures, so that it's possible e.g. to build Raspberry PI
Talos image on amd64 machine
Unpacked size comparison for amd64 (before this change, size of
`installer` was same as `imager` size):
```
REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/smira/installer v0.14.0-alpha.2-8-g73293bc2-dirty 264995cf56df 4 minutes ago 176MB
ghcr.io/smira/imager v0.14.0-alpha.2-8-g73293bc2-dirty 3ba8e0176565 6 minutes ago 616MB
```
As the `installer` image is pulled into `tmpfs` on upgrade, it's important
to have it as small as possible to avoid putting too much pressure on
node memory.
Both images are generated anyways for both `amd64` and `arm64` target
architectures.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Still no proper tags for Kubernetes modules (known issue upstream).
Also bump dependencies.
Closes#4605closes#4606
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
