OpenFaaS has released version 0.27.3, an update that makes it even easier for developers to deploy event-driven functions and microservices to Kubernetes. With OpenFaaS, developers can package their code or an existing binary in an OCI-compatible image, resulting in a highly scalable endpoint with auto-scaling and metrics.

The changelog for version 0.27.3 includes the following updates:

• PR #1816 removes duplicates and fixes the order of adopters. This contribution was made by @nitishkumar71.
• PR #1810 updates the contributing guide by removing references to the deprecated io/ioutil. This contribution was made by @testwill.

The update also includes several commits by different contributors, including:

• 9ba4a73 by @alexellis, which renames Makefile targets.
• 479285c by @nitishkumar71, which fixes adopters.
• 4cf5fb8 by @alexellis, which updates the contributing guide.
• ed5bd75 by @alexellis, which renames to OpenFaaS.
• 4f4e3d2 by @testwill, which removes references to the deprecated io/ioutil.

To see a detailed list of changes between versions 0.27.2 and 0.27.3, you can visit the comparison page.

OpenFaaS version 0.27.3 is another step forward in providing developers with a powerful and easy-to-use platform for deploying serverless functions and microservices. With its focus on Kubernetes and its extensive list of features and updates, OpenFaaS continues to be a popular choice for those interested in servers, Linux, DevOps, and home labs.

The Mixtile Cluster Box is a server enclosure designed for small business applications and edge computing. It consists of four Mixtile Blade 3 Pico-ITX single board computers (SBCs), each powered by a Rockchip RK3588 processor. The SBCs are connected to the enclosure via a 4-lane PCIe Gen3 interface through a U.2 to PCIe/SATA breakout board.

The Cluster Box has been recently released by Mixtile, following the company’s work on the software and technical details. It is available for purchase on Mixtile’s website for $339, excluding the SBCs.

The specifications of the Mixtile Cluster Box include support for up to four Mixtile Blade 3 SBCs, each with up to 32GB LPDDR4 RAM and up to 256GB eMMC flash storage. The enclosure also features a control board running OpenWrt 22.03, with a MediaTek MT7620A MIPS processor, 256MB DDR2 system memory, and 16MB SPI flash storage.

The Cluster Box includes an ASMedia ASM2824 PCIe switch with four PCIe 3.0 4-lane ports. It also provides storage interfaces through four U.2 breakout boards, with four NVMe M.2 M-Key slots (PCIe 3.0 x2 each) and four SATA 3.0 ports. Networking capabilities are offered through a Gigabit Ethernet port.

The enclosure is equipped with two 60mm fans for cooling and a power button with a blue LED indicator. It is powered by a 19 to 19.5V/4.74A power supply through a DC jack. The dimensions of the Cluster Box are 213 x 190 x 129 mm, and it is made of a metal case with SGCC steel materials. It has an operating temperature range of 0°C to 80°C and a storage temperature range of -20°C to 85°C. The relative humidity ranges from 10% to 90% during operation and 5% to 95% during storage.

Users can access the Mixtile Cluster Box through OpenWrt using SSH or a web interface. The Rockchip RK3588 boards come preloaded with a customized Linux system with Kubernetes. Control of each Mixtile Blade can be done through OpenWrt using a command called “nodectl,” which allows users to list active nodes, rescan nodes, power on/off nodes, reboot nodes, flash firmware, and enter the console of a specific node.

For more technical details and a getting started guide, users can refer to the documentation website provided by Mixtile.

Overall, the Mixtile Cluster Box offers a compact and powerful solution for building a four-node server cluster with Rockchip RK3588 SBCs. With its PCIe connectivity, storage options, and OpenWrt software, it provides a versatile platform for various server, Linux, DevOps, and home lab applications.

Source: CNX Software – Embedded Systems News.

Loki, an open source log aggregation system inspired by Prometheus, has announced the release of version v2.9.2. This highly-available, multi-tenant system is designed to be cost-effective and easy to operate.

One notable change in this release is the patching of two security vulnerabilities: CVE-2023-39325 and CVE-2023-44487. This was done by upgrading go to v1.21.3, golang.org/x/net to v0.17.0, and grpc-go to v1.56.3. For a comprehensive list of changes, users can refer to the CHANGELOG.

Loki offers two installation options: Docker container and binary.

For those who prefer the Docker container option, the images are available at https://hub.docker.com/r/grafana/loki and https://hub.docker.com/r/grafana/promtail. To install, simply run the following commands:

$ docker pull grafana/loki:2.9.2
$ docker pull grafana/promtail:2.9.2

Alternatively, Loki provides pre-compiled binary executables for various operating systems and architectures. To install the binary version, follow these steps:

$ curl -O -L "https://github.com/grafana/loki/releases/download/v2.9.2/loki-linux-amd64.zip"
$ unzip loki-linux-amd64.zip
$ chmod a+x loki-linux-amd64

Longhorn, a distributed block storage system for Kubernetes, has released its latest release candidate, Longhorn v1.4.4-rc1. This cloud-native storage solution is built using Kubernetes and container primitives.

Longhorn is known for being lightweight, reliable, and powerful. It can be easily installed on an existing Kubernetes cluster with a single kubectl apply command or by using Helm charts. Once installed, Longhorn adds support for persistent volumes to the Kubernetes cluster.

One of the key features of Longhorn is its implementation of distributed block storage using containers and microservices. It creates a dedicated storage controller for each block device volume and synchronously replicates the volume across multiple replicas stored on multiple nodes. The orchestration of these storage controllers and replicas is done using Kubernetes.

The v1.4.4-rc1 release of Longhorn introduces bug fixes and improvements, primarily focused on stability. Users are encouraged to try out the release and provide feedback. The Longhorn project appreciates all contributions.

For installation, Longhorn supports three methods: Rancher App Marketplace, Kubectl, and Helm. Detailed installation instructions can be found here.

Before upgrading to Longhorn v1.4.4 from v1.3.x/v1.4.x, it is important to read the important notes and ensure that the Kubernetes cluster is at least v1.21. The live upgrade from these source versions is not supported until the GA release. Upgrade instructions can be found here.

There are no deprecations or incompatibilities to note in this release. However, users are advised to check for any outstanding issues after the release on the Longhorn GitHub page here.

The v1.4.4-rc1 release also includes several enhancements, improvements, bug fixes, and stability and resilience updates. Notable improvements include the addition of disk status Prometheus metrics, removal of Longhorn engine path mismatch logs, and prevention of accidental deletion of Longhorn settings. A full list of these enhancements, improvements, and bug fixes can be found in the release notes.

The contributors to this release include @ChanYiLin, @PhanLe1010, @c3y1huang, and many others.

Longhorn continues to be a leading storage solution for Kubernetes, providing users with a reliable and powerful distributed block storage system. The release of Longhorn v1.4.4-rc1 brings important bug fixes and improvements, enhancing the stability of the platform. Users are encouraged to try out the release and provide feedback to further improve the Longhorn project.

Flux CD, a tool for keeping Kubernetes clusters in sync with sources of configuration like Git, has released version 2.1.2. This patch release comes with various fixes and improvements to provide users with the best experience.

One of the key fixes in this release is the faster recovery of resources such as Kustomization and HelmRelease when the source-controller has restarted and is working on restoring storage. Additionally, the source-controller now prevents failing to reconcile OCIRepositories when artifacts contain symlinks.

Another important fix addresses an issue with the helm-controller miss-labeling Custom Resource Definitions. Flux now also detects immutable field errors in Google Cloud resources managed by Kustomizations, improving the overall stability and reliability of the system.

The CLI has also seen some updates. The error reporting for flux bootstrap has been enhanced when the owner doesn’t match the identity associated with the given token. Furthermore, the flux pull artifact command now allows fetching OCI artifacts produced by other tools.

Here are the components and CLI changes in Flux CD v2.1.2:

Components Changelog

• source-controller v1.1.2
• kustomize-controller v1.1.1
• helm-controller v0.36.2

CLI Changelog

• PR #4324 - @somtochiama - bootstrap: Fix error msg when the Git token doesn’t match the repo owner
• PR #4323 - @stefanprodan - e2e: Update Go dependencies
• PR #4313 - @fluxcdbot - Update toolkit components
• PR #4296 - @Skarlso - fix: only wait for changeset if the result is not empty
• PR #4285 - @matheuscscp - Add badge for SLSA Level 3
• PR #4284 - @errordeveloper - Make flux pull work for OCI artifacts produced by other tools

Flux CD users are highly encouraged to upgrade to version 2.1.2 to benefit from these fixes and improvements.

k0s has released version v1.28.2+k0s.0. This all-inclusive Kubernetes distribution is designed for building Kubernetes clusters and comes packaged as a single binary for easy use. It can be used in various environments, including cloud, IoT gateways, Edge, and Bare metal deployments, thanks to its simple design, flexible deployment options, and modest system requirements.

The latest release, 1.28.2, includes several updates and improvements. Some of the highlights include:

• Kubernetes 1.28.2: The release builds with Kubernetes 1.28.2, and all the Kubernetes components are updated to the same version.
• Enhanced autopilot: The autopilot now allows the cluster to follow a specific update channel on an update server, making it easier to stay up-to-date with patch updates.
• SBOM generation: The release now generates a full signed SBOM (Software Bill of Materials) for each release, providing greater transparency and security.
• Extended OS testing matrix: The OS testing matrix now covers 22 OS and version combinations, including Alpine, CentOS, Debian, Fedora, Fedora CoreOS, Flatcar, Oracle, RHEL, Rocky, and Ubuntu.
• Updated component versions: Various components have been updated, including ContainerD, RunC, Etcd, Kine, Konnectivity, Kube-router, Calico, and CoreDNS.

For a detailed list of changes, you can refer to the release notes. This release also includes contributions from new contributors who made their first contribution to the project.

Overall, this release of k0s brings important updates and improvements, making it a reliable choice for building Kubernetes clusters in various environments.