Ansible-NAS VS cluster-api

Ansible-NAS

Tried it a few years ago. I had some strange error when simply trying to setup an SMB share on truenas. I immediately switched to https://github.com/davestephens/ansible-nas and haven't looked back. I feel a lot more safer and in control with ansible nas.

Ubuntu supports ZFS as well. I use this at the moment which works very well. https://github.com/davestephens/ansible-nas

Right now I manage docker mule with ansible. Traefik and dashboard is autopopulated with labels ( homepage is great, ansible-nas is sometimes outdated but can be easily fixed ) .

Never used this thing but it seems popular https://github.com/davestephens/ansible-nas freenas is fine for me

Nice UI ! I’m personally using Ansible nas , I have a private fork of it and it allowed me to custom things as I like in yaml files

- NAS software and solutions: -- FreeNas or TrueNas, I heard they are good file storage solutions, but I cross them out because I read there is limited Docker or VMs support; -- Unraid, I cross it out since needs paid license I am not sure if I need all the features. Maybe I am cheapscate, but I would like to see if I can get what I need using free software first. I probably would invest if I build a proper NAS from scratch, and not reporpusing old hardware; -- OpenMediaVault. Something I am considering, but I heard it is a decent open source NAS based on Linux, has it limitations, doesn't really like USB storage and so on. -- Synology hardware. Friend has it because he knows he has no time to mess around. Don't want to go this rout since I have the hardware already. -- Roling out your own solution or using ubuntu or ansible-nas. Sounds like a great learning experience. BUT for some reason, people who create their own solution end up switching to some different framework like this guy.

In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.

4. Having moved to a container orchestrator, all of my nodes are immutable. Hardware and VM instances _can_ be born magically into existence. Nearly all infra providers support [cluster-api](https://cluster-api.sigs.k8s.io/). Network infrastructure can now be managed with TF, so I go that route.

## Linux curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.4.4/clusterctl-linux-amd64 -o clusterctl sudo install -o root -g root -m 0755 clusterctl /usr/local/bin/clusterctl ## Mac brew install clusterctl

Did you ever try CAPI? https://github.com/kubernetes-sigs/cluster-api

You might find interesting the capi-rancher-import k8s operator we use in Sylva, it would adopt in Rancher server the Cluster API created k8s clusters (with bootstrap provider kubeadm or even rke2 - you can lookup CAPBR for the latter). I understand your clusters are not created by Cluster API, so if you could move the workloads/resources to new clusters created by Cluster API, this can come handy. (Adoption of non-CAPI clusters into CAPI is not yet a standard practice, more in https://github.com/kubernetes-sigs/cluster-api/issues/7776)

Most of the comments have mentioned older tools like kubespray, Ansible, Rancher etc. I would suggest the cloud native way using ClusterAPI or use a tool that relies on ClusterAPI in the backend called Talos

Cluster API

Sveltos is a powerful open source project that makes managing Kubernetes add-ons a breeze. It automatically discovers ClusterAPI powered clusters and allows you to easily register any other cluster (like GKE). Then, it seamlessly manages Kubernetes add-ons across all your clusters.