This Ansible-based project provisions Erhhung's high-availability Kubernetes cluster homelab
using Rancher, and installs services to monitor IoT appliances and to deploy other personal projects.
The top-level Ansible playbook main.yml
run by play.sh
will provision 5 VM hosts (rancher
and k8s1
..k8s4
)
in the existing XCP-ng Home
pool, all running Ubuntu Server 24.04 Minimal without customizations besides basic networking
and authorized SSH key for the user erhhung
.
A single-node K3s Kubernetes cluster will be installed on host rancher
alongside with Rancher Server on that cluster, and a 4-node RKE2 Kubernetes cluster with a high-availability control plane using virtual IPs will be installed on hosts
k8s1
..k8s4
. Longhorn and NFS storage provisioners will be installed in each cluster to manage a pool of LVM logical volumes on each node, and to expand the overall storage capacity on the QNAP NAS.
All cluster services will be provisioned with TLS certificates from Erhhung's private CA server at pki.fourteeners.local
or its faster mirror at cosmos.fourteeners.local
.
Service Endpoint | Description |
---|---|
https://rancher.fourteeners.local | Rancher Server console |
https://harbor.fourteeners.local | Harbor OCI registry |
https://minio.fourteeners.local | MinIO console |
https://s3.fourteeners.local | MinIO S3 API |
opensearch.fourteeners.local:9200 | OpenSearch (HTTPS only) |
https://kibana.fourteeners.local | OpenSearch Dashboards |
postgres.fourteeners.local:5432 | PostgreSQL via Pgpool (mTLS only) |
https://sso.fourteeners.local | Keycloak IAM console |
valkey.fourteeners.local:6379 valkey{1..6}.fourteeners.local:6379 |
Valkey cluster (mTLS only) |
https://grafana.fourteeners.local | Grafana dashboards |
https://metrics.fourteeners.local | Prometheus UI (Keycloak SSO) |
https://alerts.fourteeners.local | Alertmanager UI (Keycloak SSO) |
https://thanos.fourteeners.local | Thanos Query UI |
https://rule.thanos.fourteeners.local https://store.thanos.fourteeners.local https://bucket.thanos.fourteeners.local https://compact.thanos.fourteeners.local |
Thanos component status UIs |
https://kiali.fourteeners.local | Kiali console (Keycloak SSO) |
https://argocd.fourteeners.local | Argo CD console |
- K3s Kubernetes Cluster — lightweight Kubernetes distro for resource-constrained environments
- Install on the
rancher
host using the official install script
- Install on the
- Rancher Cluster Manager — provision (or import), manage, and monitor Kubernetes clusters
- Install on K3s cluster using the
rancher
Helm chart
- Install on K3s cluster using the
- RKE2 Kubernetes Cluster — Rancher's Kubernetes distribution with focus on security and compliance
- Install on hosts
k8s1
-k8s4
using the RKE2 Ansible Role with HA mode enabled
- Install on hosts
- NFS Dynamic Provisioners — create persistent volumes on NFS shares
- Install on K3s and RKE clusters using the
nfs-subdir-external-provisioner
Helm chart
- Install on K3s and RKE clusters using the
- MinIO Object Storage — S3-compatible object storage with console
- Install on main RKE cluster using the MinIO Operator and MinIO Tenant Helm charts
- Harbor Container Registry — private OCI container and Helm chart registry
- Install on K3s cluster using the
harbor
Helm chart
- Install on K3s cluster using the
- OpenSearch Logging Stack — aggregate and filter logs using OpenSearch and Fluent Bit
- Install on main RKE cluster using the
opensearch
andopensearch-dashboards
Helm charts - Instal Fluent Bit using the
fluent-operator
Helm chart andFluentBit
CR
- Install on main RKE cluster using the
- PostgreSQL Database — SQL database used by Keycloak and other applications
- Install on main RKE cluster using Bitnami's
postgresql-ha
Helm chart
- Install on main RKE cluster using Bitnami's
- Keycloak IAM & OIDC Provider — identity and access management and OpenID Connect provider
- Install on main RKE cluster using the
keycloakx
Helm chart
- Install on main RKE cluster using the
- Valkey Key/Value Store — Redis-compatible key/value store
- Install on main RKE cluster using the
valkey-cluster
Helm chart
- Install on main RKE cluster using the
- Prometheus Monitoring Stack — Prometheus (via Operator), Thanos sidecar, and Grafana
- Install on main RKE cluster using the
kube-prometheus-stack
Helm chart - Add authentication to Prometheus and Alertmanager UIs using
oauth2-proxy
sidecar - Install other Thanos components using Bitnami's
thanos
Helm chart for global querying - Enable the OTLP receiver endpoint for metrics (when needed)
- Install on main RKE cluster using the
- Istio Service Mesh with Kiali Console — secure, observe, trace, and route traffic between workloads
- Install on main RKE cluster using the
istioctl
CLI - Install Kiali using the
kiali-operator
Helm chart andKiali
CR
- Install on main RKE cluster using the
- Argo CD Declarative GitOps — manage deployment of other applications in the main RKE cluster
- Install on main RKE cluster using the
argo-cd
Helm chart
- Install on main RKE cluster using the
- Kubernetes Metacontroller — enable easy creation of custom controllers
- Install on main RKE cluster using the
metacontroller
Helm chart
- Install on main RKE cluster using the
- Ollama Server with Ollama CLI — run LLMs on Kubernetes cluster instead of locally
- Install onto
k8s1
/k8s2
with GPU passthrough using theollama
Helm chart
- Install onto
- Flowise Agentic Workflows — build AI agents using visual workflows
- Install on main RKE cluster using the
flowise
Helm chart
- Install on main RKE cluster using the
- Certificate Manager — X.509 certificate management for Kubernetes
- Install on main RKE cluster using the
cert-manager
Helm chart - Integrate with private CA
pki.fourteeners.local
using ACMEClusterIssuer
- Install on main RKE cluster using the
- OpenTelemetry Collector with Jaeger UI -- telemetry collector agent and distributed tracing backend
- Install on main RKE cluster using the OpenTelemetry Collector Helm chart
- Install Jaeger using the Jaeger Helm chart
- Velero Backup & Restore — back up and restore persistent volumes
- Install on main RKE cluster using the Velero Helm chart
- Backstage Developer Portal — software catalog and developer portal
- Meshery — visual and collaborative GitOps platform
- NATS — high performance message queues (Kafka alternative) with JetStream for persistence
- KEDA — Kubernetes Event Driven Autoscaler
The Ansible Vault password is stored in macOS Keychain under item "Home-K8s
" for account "ansible-vault
".
export ANSIBLE_CONFIG="./ansible.cfg"
VAULTFILE="group_vars/all/vault.yml"
ansible-vault create $VAULTFILE
ansible-vault edit $VAULTFILE
ansible-vault view $VAULTFILE
Some variables stored in Ansible Vault (there are many more):
Infrastructure Secrets | User Passwords |
---|---|
ansible_become_pass |
rancher_admin_pass |
github_access_token |
harbor_admin_pass |
age_secret_key |
minio_root_pass |
icloud_smtp.* |
minio_admin_pass |
k3s_token |
opensearch_admin_pass |
rke2_token |
keycloak_admin_pass |
harbor_secret |
thanos_admin_pass |
harbor_ca_key |
grafana_admin_pass |
minio_client_pass |
argocd_admin_pass |
dashboards_os_pass |
|
fluent_os_pass |
|
valkey_pass |
|
postgresql_pass |
|
keycloak_db_pass |
|
keycloak_smtp_pass |
|
monitoring_pass |
|
monitoring_oidc_client_secret.* |
|
alertmanager_smtp_pass |
|
oauth2_proxy_cookie_secret |
|
kiali_oidc_client_secret |
|
argocd_signing_key |
All managed hosts are running Ubuntu 24.04 with SSH key from https://github.com/erhhung.keys already authorized.
Ansible will authenticate as user erhhung
using private key "~/.ssh/erhhung.pem
";
however, all privileged operations using sudo
will require the password stored in Vault.
Set the config variable first for the ansible-playbook
commands below:
export ANSIBLE_CONFIG="./ansible.cfg"
-
Install required packages
1.1. Tools —
emacs
,jq
,yq
,git
, andhelm
1.2. Python — Pip packages in user virtualenv
1.3. Helm — Helm plugins: e.g.helm-diff
./play.sh packages
-
Configure system settings
2.1. Host — host name, time zone, and locale
2.2. Kernel —sysctl
params andpam_limits
2.3. Network — DNS servers and search domains
2.4. Login — customize login MOTD messages
2.5. Certs — add CA certificates to trust store./play.sh basics
-
Set up admin user's home directory
3.1. Dot files:
.bash_aliases
, etc.
3.2. Config files:htop
,fastfetch
./play.sh files
-
Install Rancher Server on single-node K3s cluster
./play.sh rancher
-
Provision Kubernetes cluster with RKE on 4 nodes
Install RKE2 with a single control plane node and 3 worker nodes, all permitting workloads,
or RKE2 in HA mode with 3 control plane nodes and 1 worker node, all permitting workloads
(in HA mode, the cluster will be accessible thru a virtual IP address courtesy ofkube-vip
)./play.sh cluster
-
Install Longhorn dynamic PV provisioner
Install MinIO object storage in HA mode6.1. Create a pool of LVM logical volumes
6.2. Install Longhorn storage components
6.3. Install NFS dynamic PV provisioner
6.4. Install MinIO tenant using NFS PVs./play.sh storage minio
-
Create resources from manifest files
IMPORTANT: Resource manifests must specify the namespaces they wished to be installed
into because the playbook simply applies each one without targeting a specific namespace./play.sh manifests
-
Install Harbor private OCI registry
./play.sh harbor
-
Install OpenSearch cluster in HA mode
9.1. Configure the OpenSearch security plugin (users and roles) for downstream applications
9.2. Install OpenSearch Dashboards UI./play.sh opensearch
-
Install Fluent Bit to ingest logs into OpenSearch
./play.sh logging
-
Install PostgreSQL database in HA mode
11.1. Run initialization SQL script to create roles and databases for downstream applications
11.2. Create users in both PostgreSQL and Pgpool./play.sh postgresql
-
Install Keycloak IAM & OIDC provider
12.1. Bootstrap PostgreSQL database with realm
homelab
, usererhhung
, and OIDC clients./play.sh keycloak
-
Install Valkey key-value store in HA mode
13.1. Deploy 6 nodes in total: 3 primaries and 3 replicas
./play.sh valkey
-
Install Prometheus, Thanos, and Grafana in HA mode
14.1. Expose Prometheus & Alertmanager UIs via
oauth2-proxy
integration with Keycloak
14.2. Connect Thanos sidecars to MinIO to store scraped metrics in themetrics
bucket
14.3. Deploy and integrate other Thanos components with Prometheus and Alertmanager./play.sh monitoring thanos
-
Install Istio service mesh in ambient mode
./play.sh istio
-
Install Argo CD GitOps delivery in HA mode
16.1. Configure Argo CD components to use the Valkey cluster for their caching needs
./play.sh argocd
-
Install Kubernetes Metacontroller add-on
./play.sh metacontroller
-
Create virtual clusters in RKE running K0s
./play.sh vclusters
Alternatively, run all playbooks automatically in order:
# pass options like -v and --step
./play.sh [ansible-playbook-opts]
# run all playbooks starting from "storage"
# ("storage" is a playbook tag in main.yml)
./play.sh storage-
Output from play.sh
will be logged in "ansible.log
".
Due to the dependency chain of the Prometheus monitoring stack (Keycloak and Valkey), the monitoring.yml
playbook must be run after most other playbooks. At the same time, those dependent services also want to create ServiceMonitor
resources that require the Prometheus Operator CRDs. Therefore, a second pass through all playbooks, starting with storage.yml
, is required to enable metrics collection on those services.
-
Shut down all/specific VMs
ansible-playbook shutdownvms.yml [-e targets={group|host|,...}]
-
Create/revert/delete VM snapshots
2.1. Create new snaphots
ansible-playbook snapshotvms.yml [-e targets={group|host|,...}] \ -e '{"desc":"text description"}'
2.2. Revert to snapshots
ansible-playbook snapshotvms.yml -e do=revert \ [-e targets={group|host|,...}] \ -e '{"desc":"text to search"}' \ [-e '{"date":"YYYY-mm-dd prefix"}']
2.3. Delete old snaphots
ansible-playbook snapshotvms.yml -e do=delete \ [-e targets={group|host|,...}] \ -e '{"desc":"text to search"}' \ -e '{"date":"YYYY-mm-dd prefix"}'
-
Restart all/specific VMs
ansible-playbook startvms.yml [-e targets={group|host|,...}]
To expand the VM disk on a cluster node, the VM must be shut down
(attempting to resize the disk from Xen Orchestra will fail with
error: VDI in use
).
Once the VM disk has been expanded, restart the VM and SSH into the node to resize the partition and LV.
$ sudo su
# verify new size
$ lsblk /dev/xvda
# resize partition
$ parted /dev/xvda
) print
Warning: Not all of the space available to /dev/xvda appears to be used...
Fix/Ignore? Fix
) resizepart 3 100%
# confirm new size
) print
) quit
# sync with kernel
$ partprobe
# confirm new size
$ lsblk /dev/xvda3
# resize VG volume
$ pvresize /dev/xvda3
Physical volume "/dev/xvda3" changed
1 physical volume(s) resized...
# confirm new size
$ pvdisplay
# show LV volumes
$ lvdisplay
# set exact LV size (G=GiB)
$ lvextend -vrL 50G /dev/ubuntu-vg/ubuntu-lv
# or grow LV by percentage
$ lvextend -vrl +90%FREE /dev/ubuntu-vg/ubuntu-lv
Extending logical volume ubuntu-vg/ubuntu-lv to up to...
fsadm: Executing resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv
The filesystem on /dev/mapper/ubuntu--vg-ubuntu--lv is now...
After expanding all desired disks, run ./diskfree.sh
to verify available disk space on all cluster nodes:
$ ./diskfree.sh
rancher
-------
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 32G 18G 13G 60% /
k8s1
----
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 50G 21G 27G 44% /
/dev/mapper/ubuntu--vg-data--lv 30G 781M 30G 3% /data
k8s2
----
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 50G 22G 26G 47% /
/dev/mapper/ubuntu--vg-data--lv 30G 781M 30G 3% /data
k8s3
----
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 50G 23G 25G 48% /
/dev/mapper/ubuntu--vg-data--lv 30G 1.2G 29G 4% /data
k8s4
----
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 50G 27G 21G 57% /
/dev/mapper/ubuntu--vg-data--lv 30G 1.2G 29G 4% /data
Ansible's ad-hoc commands are useful in these scenarios.
-
Restart Kubernetes cluster services on all nodes
ansible rancher -m ansible.builtin.service -b -a "name=k3s state=restarted" ansible control_plane_ha -m ansible.builtin.service -b -a "name=rke2-server state=restarted" ansible workers_ha -m ansible.builtin.service -b -a "name=rke2-agent state=restarted"
NOTE: remove
_ha
suffix from target hosts if the RKE cluster was deployed in non-HA mode. -
All
kube-proxy
static pods on continuousCrashLoopBackOff
This turns out to be a Linux kernel bug in
linux-image-6.8.0-56-generic
and above (discovered on upgrade tolinux-image-6.8.0-57-generic
), causing this error in the container logs:ip6tables-restore v1.8.9 (nf_tables): unknown option "--xor-mark"
Workaround is to downgrade to an earlier kernel:
# list installed kernel images ansible -v k8s_all -a 'bash -c "dpkg -l | grep linux-image"' # install working kernel image ansible -v k8s_all -b -a 'apt-get install -y linux-image-6.8.0-55-generic' # GRUB use working kernel image ansible -v rancher -m ansible.builtin.shell -b -a ' kernel="6.8.0-55-generic" dvuuid=$(blkid -s UUID -o value /dev/xvda2) menuid="gnulinux-advanced-$dvuuid>gnulinux-$kernel-advanced-$dvuuid" sed -Ei "s/^(GRUB_DEFAULT=).+$/\\1\"$menuid\"/" /etc/default/grub grep GRUB_DEFAULT /etc/default/grub ' ansible -v cluster -m ansible.builtin.shell -b -a ' kernel="6.8.0-55-generic" dvuuid=$(blkid -s UUID -o value /dev/mapper/ubuntu--vg-ubuntu--lv) menuid="gnulinux-advanced-$dvuuid>gnulinux-$kernel-advanced-$dvuuid" sed -Ei "s/^(GRUB_DEFAULT=).+$/\\1\"$menuid\"/" /etc/default/grub grep GRUB_DEFAULT /etc/default/grub ' # update /boot/grub/grub.cfg ansible -v k8s_all -b -a 'update-grub' # reboot nodes, one at a time ansible -v k8s_all -m ansible.builtin.reboot -b -a "post_reboot_delay=120" -f 1 # confirm working kernel image ansible -v k8s_all -a 'uname -r' # remove old backup kernels only # (keep latest non-working kernel # so upgrade won't install again) ansible -v k8s_all -b -a 'apt-get autoremove -y --purge'