Hello
I just created an account on the forum today because I was interested in the openmediavault (version 8.x) solution and I started testing it, so the obtained results is on fresh install.
1. Have detected issues related with data type for port:
Quotekube-system/openmediavault-traefik: Middleware.traefik.io \"https-redirect\" is invalid: spec.redirectScheme.port: Invalid value: \"integer\": spec.redirectScheme.port in body must be of type string: \"integer\""
Solution: change port number in quotes. I suppose it should be also fixed in code generator.
2. Second it will be related with kubernetes dashboard, which was retired, see: https://github.com/kubernetes-retired/dashboard and the URL was changed.
QuoteE0129 00:14:44.383728 706616 pod_workers.go:1301] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"helm\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=helm pod=helm-install-kubernetes-dashboard-s6x9f_kube-system(0b2a6409-5cd3-414b-91b7-055dc91a1898)\"" pod="kube-system/helm-install-kubernetes-dashboard-s6x9f" podUID="0b2a6409-5cd3-414b-91b7-055dc91a1898"
kubectl logs helm-install-kubernetes-dashboard-wjt6j -n kube-system
if [[ ${KUBERNETES_SERVICE_HOST} =~ .*:.* ]]; then echo "KUBERNETES_SERVICE_HOST is using IPv6" CHART="${CHART//%\{KUBERNETES_API\}%/[${KUBERNETES_SERVICE_HOST}]:${KUBERNETES_SERVICE_PORT}}"
else CHART="${CHART//%\{KUBERNETES_API\}%/${KUBERNETES_SERVICE_HOST}:${KUBERNETES_SERVICE_PORT}}"
fi
set +v -x
+ [[ '' == \v\2 ]]
+ shopt -s nullglob
+ [[ -f /config/ca-file.pem ]]
+ [[ -f /tmp/ca-file.pem ]]
+ [[ false == \t\r\u\e ]]
+ [[ false == \t\r\u\e ]]
+ [[ -n '' ]]
+ helm_content_decode
+ set -e
+ ENC_CHART_PATH=/chart/kubernetes-dashboard.tgz.base64
+ CHART_PATH=/tmp/kubernetes-dashboard.tgz
+ [[ ! -f /chart/kubernetes-dashboard.tgz.base64 ]]
+ return
+ [[ install != \d\e\l\e\t\e ]]
+ helm_repo_init
+ grep -q -e 'https\?://'
+ [[ kubernetes-dashboard/kubernetes-dashboard == stable/* ]]
+ [[ -n https://kubernetes.github.io/dashboard/ ]]
+ [[ -f /auth/username ]]
+ [[ -f /auth/tls.crt ]]
+ helm repo add kubernetes-dashboard https://kubernetes.github.io/dashboard/
Error: looks like "https://kubernetes.github.io/dashboard/" is not a valid chart repository or cannot be reached: failed to fetch https://kubernetes.github.io/dashboard/index.yaml : 404 Not FoundSolution: Probably abandoning the panel and replacing it with a more current and future proof solution.
3. I just wondering the sense of k3s in the case of single node, because the overhead is quite big although k3s is more lighter than k8s/rke2. In my opinion probably podman is the right and future proof directions here, especially for its rootless and daemon-less nature and many people is shifting from docker -> podman (main reason: security and memory pressure), k3s is for little bigger scale. One thing that is missing in podman plugin is support for compose feature like in compose plugin and we have everything 
Anyway the OMV project is really good and useful product. Kudos to everyone involved in its development. I will continue to test and explore the possibilities.
Thank you!
But of course preparing/developing plugins consumes a lot of time, so if we must choose only one (and do it as best as possible), for me it will be also k3s (especially since Docker development has slowed down, but still the solution is awesome), so I will be focus on it in my LAB environment 