XCP-ng has released version 0.3.0 of its Rust guest agent for Linux and BSD operating systems. This release includes several new features and bug fixes.

One major change is the addition of APT repositories, allowing for easy installation and updates of the guest agent on Debian-based systems. The Debian package is automatically built on Gitlab and can be accessed via a Debian repository.

The agent now has the ability to collect available and total guest memory inside FreeBSD guests. Additionally, the command line for the agent now includes two extra arguments, --stderr and --loglevel, for troubleshooting assistance. All guest agent logs are now sent to syslog by default on any Unix-like operating system.

Bug fixes include resolving an issue with plugging and unplugging a virtual NIC while the VM is online, thanks to community testing and feedback. Another bug fix removes a requirement on the libxenstore.so development symlink, now only requiring the runtime library package.

For more details, the complete changelog can be found here.

TrueNAS, the open-source storage platform developed by iXsystems, has announced the release of TrueNAS 13.0-U6.1. This update is expected to be the final version of TrueNAS 13.0, following a series that has been recognized for its stability and quality.

Incremental Improvements and Bug Fixes

TrueNAS 13.0-U6.1 includes updates to OpenZFS, addressing approximately 20 bug fixes and security improvements. Notably, this release incorporates OpenZFS 2.1.14 to correct a rarely-occurring upstream ZFS bug. The incremental improvements aim to enhance the overall performance and reliability of the platform.

Transition to TrueNAS 13.1

With TrueNAS 13.0-U6.1 serving as the concluding chapter of the 13.0 series, the development focus will shift to TrueNAS 13.1, scheduled for release in early 2024. The upcoming version is expected to maintain storage-focused features with updates to FreeBSD, OpenZFS, Samba, and other key components.

Recommendations for Users

TrueNAS recommends that existing users of TrueNAS 12.0 and TrueNAS 11.3 update their systems to TrueNAS 13.0-U6.1. This step is advised not only for resolving any software or performance issues but also to prepare for future updates, including the transition to TrueNAS 13.1 in 2024.

Current TrueNAS 13.0 users can update to U6.1 directly from the TrueNAS web UI by navigating to the System -> Update page. New users can get started by downloading the TrueNAS CORE installation media from the official website.

Looking Ahead

As TrueNAS continues to evolve, the focus remains on providing a reliable and efficient storage solution. TrueNAS Enterprise users will have the option to sidegrade to TrueNAS SCALE Enterprise 23.10 and other SCALE-based releases, catering to specific functionality requirements.

For detailed recommendations and updates, users are encouraged to refer to the TrueNAS Software Status page, which provides the latest information on stability and security releases.

Topton has unveiled an updated version of its small fanless computer, the Topton FU02, featuring an aluminum body with heat-spreading fins on the top and sides. Initially supporting up to an AMD Ryzen 7 4700U processor, the latest release introduces newer processor options, including Ryzen 5000U and Ryzen 7000U processors.

Key Features

• The highest performance version now includes the AMD Ryzen 7 7730U chip.
• While the Ryzen 7 7730U shares similarities with the Ryzen 7 5825U, it is a technically newer chip, potentially offering longer support and achieving slightly higher scores in certain synthetic benchmarks.

In addition, the Topton FU02 is available as a barebones model, starting at a base price without memory, storage, or a wireless card. Customers have the option to purchase a fully equipped model, featuring up to 64GB of dual-channel memory, up to 2TB of storage, and a WiFi 6 & Bluetooth 5.2 wireless card. The computer is designed with two SODIMM slots for DDR4-3200 memory, an M.2 2280 slot for PCIe 3.0 x4 NVMe storage, and a 2.5-inch bay for a hard drive or SSD.

Ports

The Topton FU02 features a variety of ports, including:

• 2 x Gigabit Ethernet
• 2 x HDMI 2.0
• 3 x USB 3.1 Type-C
• 2 x USB 2.0 Type-A
• 1 x 3.5mm audio

Topton highlights that the computer not only operates silently due to its fanless design but also features an aluminum enclosure that is dust and moisture-proof or at least resistant.

Source: Liliputing.

Flux CD has released version 2.2.0, a tool for keeping Kubernetes clusters in sync with sources of configuration and automating updates to configuration when there is new code to deploy. This feature release brings several updates and improvements to provide users with the best experience.

The Flux CLI and controllers have been updated to support Kustomize v5.3.0 and Kubernetes v1.28.4. This ensures compatibility with the latest versions and improves performance and stability.

One of the major updates in this release is the significant overhaul of the Flux helm-controller’s reconciliation model. This addresses persistent issues such as the automatic recovery of releases stuck in a pending state. It also improves the observability of the release status and introduces the ability to enable drift detection on a per-object basis. More details on the helm-controller improvements can be found in the Announcing Flux 2.2 GA blog post.

The Flux CLI now allows users to force or reset the reconciliation state of a HelmRelease v2beta2 object using the flux reconcile hr --force and flux reconcile hr --reset commands. This gives users more control over the deployment process.

The Flux CLI also comes with support for bootstrapping Gitea repositories, providing users with more options for managing their configuration sources. It also adds guardrails to flux install and flux bootstrap to protect users from destructive operations. Additionally, the flux version and flux check commands now print the Flux distribution version deployed on the cluster, making it easier for users to keep track of their Flux installation.

The alerting capabilities of Flux have been extended with support for NATS and Bitbucket Server & Data Center. This allows users to use these additional notification providers for alerting and monitoring purposes.

Starting with this release, Flux minor versions are benchmarked to measure the Mean Time To Production (MTTP), providing users with valuable insights into the performance of Flux.

The release is compatible with Kubernetes versions 1.26, 1.27, and 1.28.

The API changes in this release include the promotion of the HelmRelease kind from v2beta1 to v2beta2. The v2beta2 API is backwards compatible with v2beta1, and the v2beta1 API is deprecated and will be removed in a future release. Several new fields have been added, including drift detection and correction on a per-release basis, selective running of Helm tests, and a history of metadata from Helm releases. The Alert and Provider kinds have also been promoted from v1beta2 to v1beta3, with the removal of the .status field. The Bucket API now has a new field for server-side filtering of files, and the OCIRepository and HelmChart APIs have new fields for verifying OIDC identity. The HelmRepository and ImageRepository APIs have a new boolean field for connecting to non-TLS HTTP container registries.

To upgrade to Flux v2.2.0, users can either rerun the bootstrap process or use the Flux GitHub Action. The APIs can be upgraded by deploying the new CRDs and controllers and changing the manifests in Git. It is advised not to delay this procedure as the deprecated versions will be removed after 6 months.

The release also includes new documentation for the HelmRelease v2beta2 specification and a guide on enabling in-memory Kustomize builds.

Overall, Flux v2.2.0 brings several updates and improvements to provide users with a better experience in managing their Kubernetes clusters and configuration sources. Users are encouraged to upgrade to this version for the best experience.

The XCP-ng team has rolled out an updated installer for version 8.2.1, bringing various improvements.

The release includes all security and maintenance updates since the initial launch, enhanced hardware support, and drivers. Notable fixes involve AMD hardware boot failures, display issues on Intel NUC 10 and above, and compatibility with newer CPUs. The installer now supports network chipsets for home labs, includes additional optional drivers, and ensures a smoother installation process.

Users can download the latest ISOs from the official website.

Uptime Kuma, the self-hosted uptime monitor, has released version 1.23.9, bringing several improvements, bug fixes, and security fixes to the platform.

One important note is that this release may be a breaking change for those using third-party frontends or tools. The WebSocket origin now needs to be the same as your server hostname. However, users can set an environment variable called UPTIME_KUMA_WS_ORIGIN_CHECK to bypass in order to skip this check.

Here are the improvements included in this release:

• Added an aria-label to the monitor search box, improving accessibility.
• Added a helptext for the ntfy’s priority field, providing better guidance to users.

The bug fixes in this release are as follows:

• Corrected the Maintenance Start/End Time Input to Use Explicitly Specified Timezone, ensuring accurate time tracking.
• Fixed the buttons of ActionsSelect and ActionsInput that had a default type="submit", preventing unintended form submission.

In terms of security fixes, the following updates were made:

• Changing the password now closes all logged-in socket connections immediately, preventing unauthorized access.
• The WebSocket server can now only be connected from the same origin, similar to the CORS policy.
• An environment variable called UPTIME_KUMA_WS_ORIGIN_CHECK has been added, with two options: cors-like (default) and bypass.

Additionally, this release includes other small changes, code refactoring, and comment/documentation updates.