Self Documenting

The latest helm (version 3) needs its repo updated so it can find useful things like the nfs-client-provisioner chart. helm repo add stable https://kubernetes-charts.storage.googleapis.com Then we can install our containers NFS mount point.

Install helm configured to point at the AWS Storage Gateway NFS share: helm install sgbackups stable/nfs-client-provisioner --set storageClass.name=s3-backups --set nfs.server=192.168.2.21 --set nfs.path=/prox-container-backups --set nfs.mountOptions="{nolock,hard}"

To get the Argo Tunnel working in Kubernetes, we need to first install helm on the computer we run kubectl from. I use a debian based system for this, so these commands are the appropriate ones for a recent debian that has snap.

When running containers that I want available on my LAN, it's handy to expose them under their own LAN IP. To do this I set my DHCP server to stop allocating addresses past .

A few years ago I built a home NAS and virtualization server. While I moved past SmartOS after a year or two to FreeNAS, the hard drives are aging and I realized it isn't very efficient compared to what's available now.