OpenMediaVault VS Portainer

I almost forgot to mention that we need to have a NAS server accessible from the network of our Kubernetes cluster. I have my server configured on a Raspberry pi 3 where a HDD has been attached to it and has been published on the network by using Openmediavault.

You might want to consider the previously mentioned MergerFS and SnapRAID, or MDADM and LVM for your setup. OpenMediaVault [https://www.openmediavault.org/ is a solid choice in this regard. Additionally, if you're planning to run something like Proxmox, you could look into deploying Starwind CVM on top of it. Pretty much like in this guide: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-vsan-configuration-guide-for-proxmox-vsan-deployed-as-a-controller-virtual-machine-cvm/ .

You would better to install OMV instead. It's a ready to use fileserver solution with web interface.

So I'm working on a similar setup with an ancient desktop my in-laws were getting rid of. I installed OpenMediaVault directly to the hard drive (it's so old that I assume it wouldn't work too well as a hypervisor), with a 4TB external HDD attached. OMV supports Docker by means of a plug-in and I'm running a Jellyfin container with no issues at all. I'm still manually downloading everything to the HDD but *arr containers are my next step, as well as setting up a gluetun container to route all that through a VPN.

That is possible (it's automated to a certain extent). It also depends on the NAS OS. Unraid, for example, can work with drives of different sizes while using the largest one for parity. TrueNAS uses ZFS so you won't be able to just add a drive to your RAIDZ and expand it. There's also openmediavault: https://www.openmediavault.org/ that uses Linux Software RAID and you can add a new drive there but you can't combine drives of different sizes. And there's also Starwinds NAS that supports both Linux Software RAID and ZFS: https://www.starwindsoftware.com/san-and-nas. Plus, I would avoid SMR drives in RAID: https://nascompares.com/answer/list-of-wd-cmr-and-smr-hard-drives-hdd/

I'd put it like that: if you have a spare PC, then it's definitely worth trying. I would also look into openmediavault (minimal RAM needs): https://www.openmediavault.org/ and Starwinds NAS (supports both ZFS and Linux software RAID): https://www.starwindsoftware.com/san-and-nas

We see that both of our containers are working and no restarting issues. So all looks good at first glance. Now we can move to the next step. We could now deploy NTFY container, but I would like to deploy a Portainer. Why?

It's crucial to have an effective access management system that allows you to robustly manage user identities and permissions across your clusters. Although Kubernetes includes an advanced RBAC implementation, this only works within a single cluster. A dedicated Kubernetes management platform such as Rancher or Portainer is required to cohesively configure identities and grant users the multi-cluster access they require.

Check it out https://www.portainer.io/

Portainer is a container management platform that provides a powerful web interface to administer your workloads. It natively supports Kubernetes environments to help you manage your Pods, Deployments, Helm charts, and other cluster resources. Portainer also provides robust RBAC capabilities and an external authentication layer, letting you grant team members access to Kubernetes through Portainer without directly exposing your cluster.

This episode is actually why I started this series in the first place. I am an active Docker user and Docker fan, but I like containers and DevOps topics in general. I am a moderator on the official Docker forums and I see that people often struggle with the installation process of Docker CE or Docker Desktop. Docker Desktop starts a virtual machine, and the GUI is to manage the Docker CE inside the virtual machine even on Linux. Even though I prefer not to use a GUI for creating containers, I admit it can be useful in some situations, but you always need to be ready to use the command line where all the commands are available. In this episode I will use Ansible to install Docker CE in the previously created virtual machine, and I will also install a web-based graphical interface, Portainer.

Portainer

> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?

From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.

You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.

So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).

That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)

In this section, we will add Portainer to help us in managing our Docker containers. You can find more details about it here. To integrate Portainer into our EC2 project, we can follow these steps:

Git issues pointing to: https://docs.portainer.io/v/ce-2.9/start/install/agent/swarm/linux gives a ERR_TOO_MANY_REDIRECTS.