The only think that would need to be set is loadBalancerIP in servive.yaml. Other than that I think that it is pretty much Plug and Play.
### PiHole
Here I would encourage to use Unbound instead because I've started getting problems with PiHole after around a month - two. Also I needed to disable "history logging". The thing that makes querry history visible in the dashboard. I've done this because it was causing a ton of reads/writes and my 1Gbps switch didn't liked it.
nebula.yaml is for syncing between piholes
What to change:
1. line 12 and 13 in nebula.yaml. Look at nebulas github for what to set here
2. line 128 in nebula.yaml. Set correct NS
3. lines 40 to 46 in netPolicy.yaml for access to webgui
4. lines 55 to 58 in netPolicy.yaml for Nebula syncing
5. line 50 in service.yaml
6. line 12, 74 as well as 127
Note that dnsmasq-extra-data-pvc is for storing extra data about local domains to redirect a domain and all subdomain. It works like so
after that you can remove the copyFilesToPVCDeploy.yaml file and run ```kubectl apply -f /path/to/files/. -n <yourNameSpace>```
### Data
You need to change NFS share for storing shared files. Do this in deployment.yaml on line 65 and 66
This is a combination of Nginx for serving static content like files or images, and filebrowser which is a container that has a webGUI for browsing, adding and/or removing images from a folder.
Combined together webGUI for filebrowser can be placed behind an internal-only reverse proxy with internal-only domain. Nginx on the other hand can be published on the internet.
Port 80 is used for filebrowser webGUI. Port 52345 is used for exposing Nginx to the internet.