I started this deployment without checking the K3s version that Rancher needs. So before I scratched everything and restarted I tried something and documented it. It did not work for me but it could be usueful All the nodes are running version 1.25.5 of Kubernetes and Rancher’s helm chart is working only up to version …
Finally time to install Rancher! After a few seconds you will get a prompt but it is not ready yet. You can check the installation with And after it is finished verify with Open your favorite browser and browse to the FQDN. Change the password (needs to be 12 characters or more) and Welcome to …
Select an IP and an FQDN for Rancher UI and create and entry on your local DNS rancher.example.com 10.10.10.159 Load Balancer Use the ACME plugin in pfsense to request and add a certificate for rancher. Then we go to our pfsense and configure one more Virtual IP like we did in part 3 Click on …
Now let’s try to manage it from outside the cluster with kubectl. There are several options. As I did not have a ready Linux VM I tested first with Windows. All options can be found here. Windows Open a command prompt as administrator and type Close the window and open a powershell window Leave the …
Before we get started let’s create a table Variable Role Example or explanation Example IP LOAD_BALANCER_IP 10.10.10.160 LOAD_BALANCER_FQDN k3scl01 SRV1_IP_ADDRESS 10.10.10.161 SECRET_TOKEN Th1s_1s_a_v3ry_s3cr3t_t0ken_pl3as3_k33p_1t_s@f3 NODE_TOKEN Token taken from the server nodes for agent installations SRV1_DNS_NAME Master K3s-CL01-01 10.10.10.161 SRV2_DNS_NAME Master K3s-CL01-02 10.10.10.162 SRV3_DNS_NAME Master K3s-CL01-03 10.10.10.163 SRV4_DNS_NAME Worker K3s-CL01-04 10.10.10.164 SRV5_DNS_NAME Worker K3s-CL01-05 10.10.10.165 SRV6_DNS_NAME Worker …
pfsense is a free network firewall software with capabilities envied by its commercial counterparts. The load balancing mechanism is provided by a plugin called HAProxy In this configuration we have deployed two pfsense VMs, one on ESXi1 and one on ESXi2 and configured them in HA. On a previous part we made a note of …
So let’s spin up 3 Ubuntu server 22.04 VMs on our vSphere. I recommend using the Ubuntu cloud image and a VM template. To find out how to create such a VM template follow this post. We are going to need it anyway later so save some time and create it now. If you do …
NOTE: The plan was to publish all the blogs when I finished the deployment. Unfortunately, the deployment is paused due to heavy workload but I am publishing the first few parts already Planning My home lab consists of two ESXi 8.0 servers, a QNAP for Network storage, switches and firewalls. A LOT of firewalls 🙂 …
Right click on the Template and select New VM from This Template Give it a name, select the compute resource, the storage and on the clone options check on Customize this virtual machine’s hardware before clicking Next I placed 2 CPUs, 4Gb of RAM and 40Gb or storage. You can always change these options later …
Too many servers, too many equipment, too many logs to check. Better to consolidate them all in one location. Right? Splunk would be my first choice but it is quite expensive and the free tier of 500Mb is a joke. So I stumbled across Graylog . Graylog Open is free and you can install it …