The hashi-homelab was born of a desire to have a simple to maintain but very flexible homelab setup. The main goals were to keep the resources required to run the base lab setup small and to have all of the parts be easily exchangeable. For example I made the main ingress point to the service mesh a DNS round robin. While this isn't a setup I would ever use in production because it isn't the most dynamically flexible in terms of service discovery, it is however a very easy setup and if you want to launch a new mesh you just give it the Consul name service-mesh and run the job and then bam! Bob's your uncle.
make base will deploy coredns, docker-registry and haproxy these are needed for everything else to work but aside from these you can pick and choose what to deploy with make deploy-FOLDER_NAME to deploy any of the jobs from the included subfolders. make deploy-prometheus for example.
In the future I would like to provide a ready to boot image for a raspberry pi where you can run all of this as the resources needed are really minimal. With just the basics you can get away with one pi4 4gb model with plenty of room to spare.
- Scheduler: Nomad
- Service Catalog/Registry: Consul
- Service Mesh: HAProxy2
The decicision was between HAProxy and NGINX as they are both the lightest weight options however since HAPproxy 2 now supports retry logic and native Prometheus metrics, I thought I would give it a try. - DNS: CoreDNS
- Monitoring: Prometheus, Alertmanager, Telegraf, Blackbox-exporter, and Grafana
- Container Registry: Docker-Registry
...because sometimes you don't want to rely on Docker Hub being up
You need to have Nomad and Consul already running, a simple setup with the -dev flag will suffice. If don't already have a Nomad and Consul cluster, there are some excellent guides here...
https://www.nomadproject.io/guides/install/production/deployment-guide.html
https://learn.hashicorp.com/consul/datacenter-deploy/deployment-guide
There are also some files in the config folder to help you get started and also one with some services to announce so the Consul and Nomad UI are available over the service mesh.
This repo relies on a .envrc file and direnv installed or setting the environment variables manually.
Here is an .envrc example
export NOMAD_ADDR=''
export NOMAD_TOKEN=''
export VAULT_TOKEN=''
Once this is done, you simply run a make deploy-base and point your DNS to resolve via one of the Nomad nodes' IP address.
*Two of the jobs, grafana and docker-registry, use my NFS mount path of /mnt/cucumber/nomad. You can change this to your own NFS mount or if you don't have one you can pin these jobs to a particular node to have persistent storage. To change the mount path edit levant/defaults.yml and replace the volume_dir with the path to your nfs mount or other persistant storage location.
Services are exposed via http://$service_name.homelab after you point your DNS to a Nomad node.
For example, you can go to http://prometheus.homelab to visit the Prometheus UI or
http://nomad-ui.homelab to view the Nomad UI and explore the jobs.
http://consul-agent.homelab import some of the dashboards to explore around more.
http://grafana.homelab and import some of the dashboards from the repo to view your metrics.
Consul domain is switched to .home to provide separation from the mesh setup. As well as to avoid conflicts with other clusters you may already potentially interact with using the .consul default.