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.

Argo CD, a declarative continuous delivery tool for Kubernetes, has announced the release of release candidate version v2.9.0-rc2. Argo CD enables users to manage their Kubernetes applications through GitOps, providing a streamlined and efficient approach to continuous delivery of infrastructure.

The new v2.9.0 is set to introduce several new features and improvements to Argo CD. Some of the notable additions in the release candidates include:

• Support for ignoring application differences in appset
• Health status and force-sync action for PushSecret
• AnsibleJob CRD health checks
• Kustomize patches field
• Support for AzureDevops Webhooks in appset
• Dynamic rebalancing of clusters across shards
• Tree view option in output flag for app sync, app wait, and app rollback
• Automatic application of extension configs without restarting API-Server
• Addition of patch_ms and setop_ms timings to reconciliation logs
• Button for wrapping lines in pod logs viewer in the UI
• Tree view option in output flag for app get and app resources CLI commands
• Support for preserving labels and global fields in appset
• Enablement of haproxy metrics through Helm Chart
• Shorthand flags for follow and container in app logs
• Additional environment variable for cluster cache list page buffer size
• Improved RBAC support for discovery/sync
• Addition of Dott to users
• Upgraded notification engine
• Support for extra attributes for opentelemetry
• Parallel execution of refresh from UI
• Topic filter for Gitlab SCM in appset
• Timeout option for update cluster info
• Support for apply out of sync flag only in CLI
• Support for AzureDevops Webhooks
• SCM Provider option for Gitlab generator to filter shared projects from subgroups projects
• Short revision in ARGOCD_APP_REVISION_SHORT env variable
• Integration of kubelogin capability to argocd-k8s-auth
• Alias application as apps for consistency with notifications engine
• Restriction of SCM provider URLs
• Autosync_enabled field in the argocd_app_info gauge
• Support for self-signed TLS/Certificates for Gitlab SCM Provider
• Respect RBAC for resource exclusions/inclusions

In addition to these new features, the rc2 release candidate includes various bug fixes and improvements.

For a complete list of changes and enhancements being introduced in v2.9.0, users can refer to the full changelogs of v2.9.0-rc1 and v2.9.0-rc2.

k0s, an all-inclusive Kubernetes distribution, has just released version v1.27.6+k0s.0. This distribution is designed to make building a Kubernetes cluster easier by providing all the necessary features in a single binary. One of the key advantages of k0s is its versatility. While it is well-suited for cloud environments, it can also be used in IoT gateways, edge deployments, and bare metal setups. This is due to its simple design, flexible deployment options, and modest system requirements.

In this latest release, several changes and improvements have been made. These include fixing a hanging start-stop-daemon in footloose Alpine, updating dependencies such as filepath-securejoin and Go, modifying kubelet arguments passed in the CLI inttest, and upgrading containerd to version 1.7.6. Additionally, Kubernetes itself has been bumped to version 1.27.6.

For more details on the changes, you can check out the full changelog.