K3s, a lightweight and highly available certified Kubernetes distribution, has released version v1.28.3+k3s2. This version is designed for production workloads in resource-constrained and remote locations, as well as inside IoT appliances. K3s comes as a single binary that is less than 70MB in size, making it easy to install, run, and auto-update a production Kubernetes cluster.

The latest release updates Kubernetes to version v1.28.3 and addresses several issues. Some of the changes since v1.28.3+k3s1 include:

• Restoration of selinux context systemd unit file
• Update of channel to v1.27.7+k3s1
• Bump of Sonobuoy version
• Bump of Trivy version
• Fix for accessing outer scope .SystemdCgroup, which resolves issues with starting with nvidia-container-runtime
• Upgrade of traefik chart to v25.0.0
• Update of traefik to fix registry value
• Improvement to not use iptables-save/iptables-restore if it will corrupt rules

The components and versions included in this release are as follows:

• Kubernetes v1.28.3
• Kine v0.10.3
• SQLite 3.42.0
• Etcd v3.5.9-k3s1
• Containerd v1.7.7-k3s1
• Runc v1.1.8
• Flannel v0.22.2
• Metrics-server v0.6.3
• Traefik v2.10.5
• CoreDNS v1.10.1
• Helm-controller v0.15.4
• Local-path-provisioner v0.0.24

For more information on the release and its features, refer to the Kubernetes release notes.

Overall, this new release of K3s brings important updates and fixes to enhance the performance and reliability of Kubernetes clusters in production environments.

Source: K3s

Longhorn has released version v1.4.4, a distributed block storage system for Kubernetes. This release includes various enhancements, improvements, bug fixes, and stability and resilience updates. Some of the notable improvements include the addition of disk status Prometheus metrics, improved log levels for resource update failures, and support for both NFS hard and soft with custom timeo and retrans options for RWX volumes. Bugs related to volume synchronization, attaching/detaching loops, and volume mounting have also been addressed. This release is aimed at providing a more stable and reliable storage solution for Kubernetes environments. For more information, you can visit the Longhorn v1.4.4 release page.

Netmaker has released its latest version, v0.21.1, of their WireGuard mesh VPN. Netmaker is a platform that automates the creation of fast, secure, and distributed virtual networks.

With Netmaker, users can easily create virtual networks between data centers, clouds, and edge devices without the need for manual configuration. This automation saves time and effort for users, allowing them to focus on other important tasks.

One of the key features of Netmaker is its integration with Kernel WireGuard, which provides maximum speed, performance, and security. This ensures that the virtual networks created with Netmaker are not only efficient but also highly secure.

Netmaker is designed to scale from small businesses to enterprise-level organizations. This means that whether you are a small startup or a large corporation, Netmaker can meet your networking needs.

One of the standout features of Netmaker is its ability to be highly customized. Users can configure Netmaker with WireGuard for various use cases, such as peer-to-peer connections, site-to-site connections, Kubernetes deployments, and more. This flexibility allows users to tailor Netmaker to their specific requirements.

The latest version, v0.21.1, brings several new features and fixes to the Netmaker platform:

What’s New in v0.21.1:

• Remote access client session management: Users now have more control over managing remote access client sessions. Refer to the users section in the documentation for more details.
• Generic DNS entries: It is now possible to create generic DNS entries, providing more flexibility in configuring DNS settings.
• Upgrade client version: Users can now easily upgrade the client version to match the server version directly from the user interface.
• Moved PersistentKeepAlive setting: The PersistentKeepAlive setting has been moved from the node level to the host level, simplifying network configuration.

What’s Fixed in v0.21.1:

• Extclients DNS properly set: The issue of Extclients DNS not being properly set from the ingress DNS value provided has been resolved.
• Role update of OAuth user allowed: Users can now update the role of an OAuth user without any issues.
• Zombie node issue fixed: The issue of zombie nodes has been fixed, ensuring a smoother user experience.

Despite the improvements in v0.21.1, there are still a few known issues that users should be aware of:

• Windows installer does not install WireGuard: Users running the Windows installer may encounter an issue where WireGuard is not installed automatically. This can be resolved by manually installing WireGuard.
• netclient-gui error dialog: If the Netmaker server is offline, the netclient-gui application will continuously display an error dialog. This is a known issue that will be addressed in future releases.
• Mac IPv6 addresses/route issues: Mac users may experience issues with IPv6 addresses and routes. This is a known issue that is currently being investigated.
• Docker client re-join issue: Users may encounter difficulties when trying to re-join a network using the Docker client after complete deletion. This issue is currently being addressed.
• netclient-gui network tab blank: After disconnecting from a network, the network tab in the netclient-gui application may appear blank. This is a known issue that will be fixed in future updates.

Despite these known issues, Netmaker’s latest release, v0.21.1, brings several new features and fixes that further enhance its capabilities as a WireGuard mesh VPN solution. With its automation, scalability, and customization options, Netmaker continues to be a valuable tool for those interested in servers, Linux, DevOps, and home labs.

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.

Caddy has released version v2.7.5 of its web server.

This release includes several bug fixes and improvements, including a fix for the HTTP/2 Rapid Reset issue that affected most HTTP/2 implementations. The update also includes an upgrade to quic-go from v0.37.5 to v0.39.0, which brings many performance improvements. The QUIC_GO_DISABLE_GSO and QUIC_GO_DISABLE_ECN environment variables can now be used to disable GSO and ECN if they cause problems. The file server’s fileserver.BrowseTemplate is now exported, allowing it to be customized by programs embedding Caddy. Environment variables loaded with --envfile no longer override existing variables. The encode handler now compresses application/wasm* content types by default. The reverse_proxy handler now has the ability to emit detailed logs for debugging streaming and buffering by setting the verbose_logs subdirective and logging to debug level. The version can now be checked with caddy -v, similar to other CLI utilities.

Caddy is currently on feature freeze until after version 2.8 to improve testing. The full changelog for version v2.7.5 can be found here.

The latest version of the cloud native application proxy, Traefik, has been released. Version v2.10.5 brings several bug fixes and documentation updates to improve the functionality and user experience of the proxy.

Bug fixes in this release include:

• Move origin fields capture to service level
• Fix preflight response status in access logs
• Update go-acme/lego to v4.14.0
• Update go-acme/lego to v4.13.3
• Update quic-go to v0.37.5
• Update quic-go to v0.39.0
• Update quic-go to v0.37.6
• Update quic-go to v0.38.0
• Update quic-go to v0.38.1
• Ignore ErrKeyNotFound error for the KV provider
• Adjust forward auth to avoid connection leak
• Improve CNAME flattening to avoid unnecessary error logging
• Allow X-Forwarded-For delete operation
• Update x/net and grpc/grpc-go
• Add missing accessControlAllowOriginListRegex to middleware view
• Fix false positive in URL anonymization

Documentation updates in this release include:

• Change Arvancloud URL
• Correct minor typo in crd-acme docs
• Remove healthcheck interval configuration warning
• Docs describe the missing db parameter in Redis provider
• Doc fix accessControlAllowHeaders examples
• Updates business callout in the documentation

These bug fixes and documentation updates contribute to a smoother and more efficient experience for users of Traefik. The latest version can be downloaded from the official Traefik GitHub repository.