K3s is simply another lightweight container runtime beside Docker. The k8s plugin does not want to make use of extra features that are available in k8s; this does not make sense on a one node cluster.
But nevertheless you have nice features.
Here are some more comments.
Why K8s with K3s:
Sooner or later K8s will also become the standard in the home sector because it is simply much more extensible than Docker Compose. Even if you only run it as a one node system, you can benefit from the huge ecosystem of Kubernetes.
Therefore the OMV project will focus on extending the K8s recipes as this will make it much easier to run new software in OMV. Conventional plugin development is much more time consuming. The K8s plugin will get some nice enhancements in the near future which will simplify the installation of software.
Thanks for this info and all the work you are doing votdev
I use docker and compose a lot but I did have a go using the k8s plugin. There is so much going on with all of the info and config. I did find it hard but managed to get a few containers up and running.
It’s a big learning curve but I look forward to what’s coming next. I think the plugin would benefit from a UI layer in front of all the complexity so that less experienced users can use it more easily.
I think the plugin would benefit from a UI layer in front of all the complexity so that less experienced users can use it more easily.
I will try to improve the UI to install software, but when it comes to management, OMV will rely on 3rd party solutions like Rancher or K8s Dashboard because the project does not have the capacity to do that (and I will not reinvent the wheel).
I understand. That sounds good
Don’t have an account yet? Register yourself now and be a part of our community!
