News

openmediavault 6.9.15

• Several improvements (backported enhancements and fixes from OMV7).

openmediavault 7.0.4

• Replace hdparm with smartctl in UDEV helper script.

openmediavault-k8s 7.0-5

• Several improvements

openmediavault-usbbackup 7.0.2

• Replace hdparm with smartctl to spin down hard disks after the backup job is done.

The openmediavault-k8s-recipes GitHub repository has been created to contain the K8s recipes that can be consumed by the openmediavault-k8s plugin. I hope for active help from the community to fill this recipe collection with many templates of popular containerized applications. Anyone who would like to contribute should simply submit a PR here.

Check the README for the rules of the recipes. You might also check out the K3s documentation how to use Helm charts in your recipes. Use the already existing recipes as templates.

openmediavault 7.0.2

• Fix problem when deploying file system quota.
• Issue #1725: Add search field to shared folder page.

A preview of the K8s plugin for openmediavault has been released. If you want to run your Docker containers in a Kubernetes environment with all the advantages that Docker or Podman does not offer, then this plugin is for you.

The plugin is based on the amazing SUSE K3s, a lightweight Kubernetes distribution built for IoT & Edge computing which makes it ideally for running on SBC like Raspberry Pi. The plugin comes with pre-installed cert-manager and Traefik. The Kubernetes Dashboard is available at port 4443 by default. PersistentVolumes (PV) will be auto-created for existing shared folders which will make it easy to consume them via PersistentVolumeClaims (PVC) in your deployments. The LoadBalancer service is running on port 8080 and 8443 by default. You can use your local SSL certificates that are managed via the openmediavault UI, or let cert-manager auto-create a self-signed certificate. Your installed apps can then be reached via subpath like https://<MY.DOMAIN>:8443/<APP> or a dedicated NodePort if the application does not provide the ability to run behind a reverse proxy. The plugin is using the embedded etcd to have the ability to expand the single-node cluster with additional nodes. However, this is not the main goal as explained below.

The plugin is designed for use as a single-node to offer users the simple option of using their containers in a Kubernetes environment. The goal is not to build a multi-node infrastructure with it. There is other software for this and this would go beyond the main goal of openmediavault, namely to offer the user a simple NAS solution for SOHO use. Therefore, the whole UI and the infrastructure in the background is designed to install things automatically for the user so that he wants to concentrate on installing the applications. Users who want to customize their Kubernetes environment are not the target of this plugin. The UI will be kept simple. It is only intended to provide a quick overview of the most frequently used resources, to view them and delete them if necessary. The main work should be done using CLI, K9s, Kubernetes Dashboard or other solutions.

At a later stage, it is planned to provide an infrastructure that provides recipes that allow users to easily choose from a selection of applications that they want to install. These recipes are intended to serve as a template for installing known applications without any great knowledge of Kubernetes. These can then be based on Helm charts or, for example, simply on deployments. However, the aim is always to make the configuration as simple as possible for the user.

Any help from the community is welcome for this collection of recipes. Further information will be announced in the near future.

To install the plugin, simply choose the openmediavault-k8s one in the plugin page of the openmediavault UI.

Also check out the this forum post or the plugin live in action.