Skip to content

v0.21.0

Latest
Latest

Choose a tag to compare

View all tags
@bfjelds bfjelds released this 02 Mar 17:49
v0.21.0
e392693
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Full version: 0.21.2026022501-ve392693

New Features

Sysext, Confext, and Netplan servicing without reboot

Trident supports runtime updates, which allow configuration changes of extensions and netplans to be applied to the servicing OS without requiring a full OS image update.

To utilize, modify the existing Host Configuration's os.systexts, os.confexts, and/or os.netplans sections (if any other sections are modified, Trident will begin an A/B update).

Health checks can be utilized to validate runtime updates. If health checks are configured in the Host Configuration, Trident runs them to verify that the update was successful. Ensure that health checks are configured to run on runtime updates by specifying runtime-update after runsOn. If any health check fails, the runtime update will be rolled back.

For more information, see the Runtime Updates documentation.

Manual Rollback

Trident now provides an API to rollback previously applied updates. Users can:

Command Description
trident get rollback-chain Query for available rollbacks
trident rollback --check Query if the last update was an ab or runtime
trident rollback Undo whatever the last update was
trident rollback --runtime Undo runtime updates in the servicing OS one at a time
trident rollback --ab Undo the last A/B update

For more information, see the Manual Rollback documentation.

Diagnose

Trident now provides an API to collect helpful logs and system information. Use trident diagnose to help diagnose any issues.

For more information, see the Generate a Diagnostics Bundle documentation.

Tracing to Journald

Trident tracing is now added to Journald. The tracing entries are stored with a syslog-id of trident-tracing.

To retrieve, as json for example, use a command like journalctl -t trident-tracing -o json

Trident log explorer helps diagnose issues

Trident has introduced the log explorer to help interpret the log files Trident produces. With the log explorer, it is easy to find errors or warnings. Log entries are helpfully parsed to be more user-friendly and readable.

gRPC API

Trident now supports running as a daemon that responds to gRPC requests over a local Unix socket. In this first version with gRPC support only a limited subset of functionality is supported, but it will be expanded to cover all of Trident's features in the future.
The gRPC services available in this release are described in the gRPC protobuf definitions.

The Trident RPM now includes tridentd.socket and tridentd.service to enable this functionality. By default, the Trident socket exists at /run/trident/trident.sock and is only accessible to the root user.

More info.

Disk Streaming

A new servicing type to bootstrap hosts with Trident. Whereas the regular install process requires a Host Configuration to drive the provisioning, the disk streaming process only requires a COSI (v1.2+) file. Trident will use the COSI metadata to re-create the disk the COSI file was made from in a disk in the target node. Functionally, it is similar to applying a raw image onto a disk to "install" an OS, but with the advantages of size, compression, and efficiency of COSI and Trident.

More info.

Other Updates

COSI download optimizations

The trident downloader has also been improved to be more resilient to network issues that might arise in the middle of COSI downloads.

Bug Fixes

  • Trident errors have been reformated to fix some context issues: #510
  • Validate extension paths in Host Configuration: #387

Known Issues

  • ImageCustomizer v1.2.0 produces UKI COSI files that are only compatible with Trident v0.21.0+. Trident v0.21.0 works with COSI files created by any recent ImageCustomizer.
  • In this release, new integration with systemd-journald was added to directly send logs to the system journal. However, this implementation is not compatible with chrooted environments, which causes Trident logs produced during the chroot steps to be missing from the system journal. All logs are still available in the background log file.

Links

Assets 3
Loading