From afe1e4b0ebcb6a117aa9dc781a9ffedb3a807db0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Wed, 29 Jan 2025 08:03:13 +0200 Subject: Update content for html --- ...4-11-17-f3s-kubernetes-with-freebsd-part-1.html | 10 +- .../DRAFT-f3s-kubernetes-with-freebsd-part-3.html | 6 +- gemfeed/atom.xml | 12 +- gemfeed/f3s-kubernetes-with-freebsd-part-4.html | 324 +++++++++++++++++++++ 4 files changed, 342 insertions(+), 10 deletions(-) create mode 100644 gemfeed/f3s-kubernetes-with-freebsd-part-4.html (limited to 'gemfeed') diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html index b3a4f327..17fe5878 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.html @@ -23,6 +23,7 @@ View this page as My previous setup was great for learning Terraform and AWS, but it is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety percent of the time and still cost around $20 monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper in terms of electricity consumption. I have a 50 MBit/s uplink (I could have more if I wanted, but it is plenty for my use case already).

-From babylon5.buetow.org to .cloud
+From babylon5.buetow.org to .cloud

Migrating off all my containers from AWS ECS means I need a reliable and scalable environment to host my workloads. I wanted something:

@@ -111,8 +112,8 @@ View this page as Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email.

-KISS server monitoring with Gogios
+KISS server monitoring with Gogios

Ironically, I implemented Gogios to avoid using more complex alerting systems like Prometheus, but here we go—it integrates well now.

@@ -181,6 +182,7 @@ View this page as 2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage
2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4

f3s logo

@@ -251,6 +252,8 @@ END APC : 2025-01- Of course, this won't work when f0 is down. In this case, no operational node would be connected to the UPS via USB; therefore, the current power status would not be known. However, I consider this a rare circumstance. Furthermore, in case of an f0 system crash, sudden power outages on the two other nodes would occur at different times, making real data loss (the main concern here) effectively impossible.

+And if f0 is down and f1 and f2 receive new data and crash midway, it's likely that a client (e.g., an Android app or another laptop) still has the data stored on it, making data loss recoverable. I'd receive an alert if any of the nodes go down (more on monitoring later in this blog series).
+

Installation on partners



To do this, I installed apcupsd via doas pkg install apcupsd on f1 and f2, and then I could connect to it this way:
@@ -374,7 +377,7 @@ http://www.gnu.org/software/src-highlite --> Broadcast Message from root@f0.lan.buetow.org (no tty) at 15:08 EET... - *** FINAL System shutdown message from paul@f1.lan.buetow.org *** + *** FINAL System shutdown message from root@f0.lan.buetow.org *** System going down IMMEDIATELY @@ -408,6 +411,7 @@ Jan 26 17:36:32 f2 apcupsd[2159]: apcupsd shutdown succeeded 2024-04-01 KISS high-availability with OpenBSD
2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage
2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4

E-Mail your comments to paul@nospam.buetow.org :-)

diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 1a7d9632..04c16049 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-01-19T13:21:25+02:00 + 2025-01-29T08:02:28+02:00 foo.zone feed To be in the .zone! @@ -1061,6 +1061,7 @@ dev.cpu.0.freq: 2922
2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)
2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4

f3s logo

@@ -1090,7 +1091,7 @@ dev.cpu.0.freq: 2922
My previous setup was great for learning Terraform and AWS, but it is too expensive. Costs are under control there, but only because I am shutting down all containers after use (so they are offline ninety percent of the time and still cost around $20 monthly). With the new setup, I could run all containers 24/7 at home, which would still be cheaper in terms of electricity consumption. I have a 50 MBit/s uplink (I could have more if I wanted, but it is plenty for my use case already).

-From babylon5.buetow.org to .cloud
+From babylon5.buetow.org to .cloud

Migrating off all my containers from AWS ECS means I need a reliable and scalable environment to host my workloads. I wanted something:

@@ -1149,8 +1150,8 @@ dev.cpu.0.freq: 2922
So, when I want to access a service running in k3s, I will hit an external DNS endpoint (with the authoritative DNS servers being the OpenBSD boxes). The DNS will resolve to the master OpenBSD VM (see my KISS highly-available with OpenBSD blog post), and from there, the relayd process (with a Let's Encrypt certificate—see my Let's Encrypt with OpenBSD and Rex blog post) will accept the TCP connection and forward it through the WireGuard tunnel to a reachable node port of one of the k3s nodes, thus serving the traffic.

-KISS high-availability with OpenBSD
-Let's Encrypt with OpenBSD and Rex
+KISS high-availability with OpenBSD
+Let's Encrypt with OpenBSD and Rex

The OpenBSD setup described here already exists and is ready to use. The only thing that does not yet exist is the configuration of relayd to forward requests to k3s through the WireGuard tunnel(s).

@@ -1190,7 +1191,7 @@ dev.cpu.0.freq: 2922
Alerts generated by Prometheus are forwarded to Alertmanager, which I will configure to work with Gogios, a lightweight monitoring and alerting system I wrote myself. Gogios runs on one of my OpenBSD VMs. At regular intervals, Gogios scrapes the alerts generated in the k3s cluster and notifies me via Email.

-KISS server monitoring with Gogios
+KISS server monitoring with Gogios

Ironically, I implemented Gogios to avoid using more complex alerting systems like Prometheus, but here we go—it integrates well now.

@@ -1219,6 +1220,7 @@ dev.cpu.0.freq: 2922 2024-04-01 KISS high-availability with OpenBSD
2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage (You are currently reading this)
2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+f3s-kubernetes-with f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4

E-Mail your comments to paul@nospam.buetow.org :-)

diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-4.html b/gemfeed/f3s-kubernetes-with-freebsd-part-4.html new file mode 100644 index 00000000..a09723d0 --- /dev/null +++ b/gemfeed/f3s-kubernetes-with-freebsd-part-4.html @@ -0,0 +1,324 @@ + + + + +f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4 + + + + + +

+View this page as Markdown | Gemini +

+

f3s: Kubernetes with FreeBSD - Rocky Linux Bhyve VMs - Part 4


+
+This is the thourth blog post about my f3s series for my self-hosting demands in my home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution we will use on FreeBSD-based physical machines.
+
+2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage
+2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+
+f3s logo
+
+

Table of Contents


+
+
+

Introduction


+
+In this blog post, we are going to install the Bhyve hypervisor.
+
+The FreeBSD Bhyve hypervisor is a lightweight, modern hypervisor that enables virtualization on FreeBSD systems. Bhyve's strengths include its minimal overhead, which allows it to achieve near-native performance for virtual machines. It is designed to be efficient and lightweight, leveraging the capabilities of the FreeBSD operating system for performance and network management.
+
+Bhyve supports running a variety of guest operating systems, including FreeBSD, Linux, and Windows, on hardware platforms that support hardware virtualization extensions (such as Intel VT-x or AMD-V). In our case, we are going to virtualize Rocky Linux, which later on in this series will be used to run k3s.
+
+

Basic Bhyve setup


+
+For the management of the Bhyve VMs, we are using vm-bhyve, a tool not part of the FreeBSD operating system but available as a ready-to-use package. It eases VM management and reduces a lot of the overhead. We also install the required package to make Bhyve work with the UEFI firmware.
+
+https://github.com/churchers/vm-bhyve
+
+The following commands are executed on all three hosts f0, f1, and f2, where re0 is the name of the Ethernet interface (which may need to be adjusted if your hardware is different):
+
+ +
paul@f0:~ % doas pkg install vm-bhyve bhyve-firmware
+paul@f0:~ % doas sysrc vm_enable=YES
+vm_enable:  -> YES
+paul@f0:~ % doas sysrc vm_dir=zfs:zroot/bhyve
+vm_dir:  -> zfs:zroot/bhyve
+paul@f0:~ % doas zfs create zroot/bhyve
+paul@f0:~ % doas vm init
+paul@f0:~ % doas vm switch create public
+paul@f0:~ % doas vm switch add public re0
+
+
+Bhyve stores all it's data in the /bhyve of the zroot ZFS pool:
+
+ +
paul@f0:~ % zfs list | grep bhyve
+zroot/bhyve                                   1.74M   453G  1.74M  /zroot/bhyve
+
+
+For convenience, we also create this symlink:
+
+ +
paul@f0:~ % doas ln -s /zroot/bhyve/ /bhyve
+
+
+
+Now, Bhyve is ready to rumble, but no VMs are there yet:
+
+ +
paul@f0:~ % doas vm list
+NAME  DATASTORE  LOADER  CPU  MEMORY  VNC  AUTO  STATE
+
+
+

Rocky Linux VMs


+
+

ISO download


+
+We're going to install the Rocky Linux from the latest minimal iso:
+
+ +
paul@f0:~ % doas vm iso \
+ https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.5-x86_64-minimal.iso
+/zroot/bhyve/.iso/Rocky-9.5-x86_64-minimal.iso        1808 MB 4780 kBps 06m28s
+paul@f0:/bhyve % doas vm create rocky
+
+

VM configuration


+
+The default configuration looks like this now:
+
+ +
paul@f0:/bhyve/rocky % cat rocky.conf
+loader="bhyveload"
+cpu=1
+memory=256M
+network0_type="virtio-net"
+network0_switch="public"
+disk0_type="virtio-blk"
+disk0_name="disk0.img"
+uuid="1c4655ac-c828-11ef-a920-e8ff1ed71ca0"
+network0_mac="58:9c:fc:0d:13:3f"
+
+
+Whereas the uuid and the network0_mac differ on each of the 3 hosts.
+
+but in order to make Rocky Linux boot it (plus some other adjustments, e.g. as I am intending to run the majority of the workload in the k3s cluster running on those linux VMs, I give them beefy specs like 4 CPU cores and 14GB RAM), I run doas vm configure rocky and modified it to:
+
+
+guest="linux"
+loader="uefi"
+uefi_vars="yes"
+cpu=4
+memory=14G
+network0_type="virtio-net"
+network0_switch="public"
+disk0_type="virtio-blk"
+disk0_name="disk0.img"
+graphics="yes"
+graphics_vga=io
+uuid="1c45400b-c828-11ef-8871-e8ff1ed71cac"
+network0_mac="58:9c:fc:0d:13:3f"
+
+
+

VM installation


+
+To start the installer from the downloaded ISO, I run:
+
+ +
paul@f0:~ % doas vm install rocky Rocky-9.5-x86_64-minimal.iso
+Starting rocky
+  * found guest in /zroot/bhyve/rocky
+  * booting...
+
+paul@f0:/bhyve/rocky % doas vm list
+NAME   DATASTORE  LOADER  CPU  MEMORY  VNC           AUTO  STATE
+rocky  default    uefi    4    14G     0.0.0.0:5900  No    Locked (f0.lan.buetow.org)
+
+paul@f0:/bhyve/rocky % doas sockstat -4 | grep 5900
+root     bhyve       6079 8   tcp4   *:5900                *:*
+
+
+Port 5900 now also opened for VNC connections, so I connected to it with a VNC client and run through the installation dialogs. I'm sure this could be done unattended or more automated, there are only 3 VMs to install, and the automation doesn't seem worth it as we are doing it only once in a year or less often.
+
+

Increase of the disk image


+
+By default the VMs disk image is only 20G, which is a bit small for my purposes, so I stopped the VMs again and run truncate on the image file to enlarge them to 100G, and re-started the installation:
+
+ +
paul@f0:/bhyve/rocky % doas vm stop rocky
+paul@f0:/bhyve/rocky % doas truncate -s 100G disk0.img
+paul@f0:/bhyve/rocky % doas vm install rocky Rocky-9.5-x86_64-minimal.iso
+
+
+

Connect to VPN


+
+For the installation, I opened the VPN client on my Fedora laptop (GNOME comes with a simple VPN client) and ran through the base installation for each of the VMs manually. Again, I am sure this could have been automated a bit more, but there were just 3 VMs, and it wasn't worth the effort. The three VNC addresses of the VMs were: vnc://f0:5900, vnc://f1:5900, and vnc://f0:5900.
+
+I mostly selected the default settings (auto partitioning on the 100GB drive and a root user password). After the installation, the VMs were rebooted.
+
+

After install


+
+I performed the following steps for all 3 VMs. In the following, the examples are all executed on f0 (bzw the VM r0 running on f0):
+
+

VM auto-start after host reboot


+
+To automatically start the VM on the servers I added the following to the rc.conf on the FreeBSD hosts:
+
+ +
paul@f0:/bhyve/rocky % cat <<END | doas tee -a /etc/rc.conf
+vm_list="rocky"
+vm_delay="5"
+
+
+The vm_delay isn't really required. It is used to wait 5 seconds before starting each VM, but as of now, there is only one VM per host. Maybe later, when there are more, this will be useful to have. After adding, there's now a Yes indicator in the AUTO column.
+
+ +
paul@f0:~ % doas vm list
+NAME   DATASTORE  LOADER  CPU  MEMORY  VNC           AUTO     STATE
+rocky  default    uefi    4    14G     0.0.0.0:5900  Yes [1]  Running (2063)
+
+
+

Static IP configuration


+
+After that, I changed the network configuration of the VMs to be static (from DHCP) here. As per previous post of this series, the 3 FreeBSD hosts were already in my /etc/hosts file:
+
+
+192.168.1.130 f0 f0.lan f0.lan.buetow.org
+192.168.1.131 f1 f1.lan f1.lan.buetow.org
+192.168.1.132 f2 f2.lan f2.lan.buetow.org
+
+
+For the Rocky VMs I added those to the FreeBSD hosts systems as well:
+
+ +
paul@f0:/bhyve/rocky % cat <<END | doas tee -a /etc/hosts
+192.168.1.120 r0 r0.lan r0.lan.buetow.org
+192.168.1.121 r1 r1.lan r1.lan.buetow.org
+192.168.1.122 r2 r2.lan r2.lan.buetow.org
+END
+
+
+and configured the IPs accordingly on the VMs themselves by opening a root shell via RDP to the VMs and entering the following commands on each of the VMs:
+
+ +
[root@r0 ~] % dnmcli connection modify enp0s5 ipv4.address 192.168.1.120/24
+[root@r0 ~] % dnmcli connection modify enp0s5 ipv4.gateway 192.168.1.1
+[root@r0 ~] % dnmcli connection modify enp0s5 ipv4.dns 192.168.1.1
+[root@r0 ~] % dnmcli connection modify enp0s5 ipv4.method manual
+[root@r0 ~] % dnmcli connection down enp0s5
+[root@r0 ~] % dnmcli connection up enp0s5
+[root@r0 ~] % hostnamectl set-hostname r0.lan.buetow.org
+[root@r0 ~] % cat <<END >>/etc/hosts
+192.168.1.120 r0 r0.lan r0.lan.buetow.org
+192.168.1.121 r1 r1.lan r1.lan.buetow.org
+192.168.1.122 r2 r2.lan r2.lan.buetow.org
+END
+
+
+Whereas:
+
+
    +
  • 192.168.1.120 is the IP of the VM itself (here: r0.lan.buetow.org)
    • +
  • 192.168.1.1 is the address of my home router, which also does DNS.
    • +

+

Permitting root login


+
+As these VMs arent directly reachable via SSH from the internet, I enabled root login by adding a line with PermitRootLogin yes to /etc/sshd/sshd_config.
+
+Once done, I rebooted the VM by running reboot inside of the vm to test whether everything was configured and persisted correctly.
+
+After reboot, I copied my public key from my Laptop to the 3 VMs:
+
+ +
% for i in 0 1 2; do ssh-copy-id root@r$i.lan.buetow.org; done
+
+
+And then I edited the /etc/ssh/sshd_config file again on all 3 VMs and configured PasswordAuthentication no, to only allow SSH key authentication from now on.
+
+

Install latest updates


+
+ +
[root@r0 ~] % dnf update
+[root@r0 ~] % dreboot
+
+
+CPU STRESS TESTER VM VS NOT VM
+
+Other *BSD-related posts:
+
+2016-04-09 Jails and ZFS with Puppet on FreeBSD
+2022-07-30 Let's Encrypt with OpenBSD and Rex
+2022-10-30 Installing DTail on OpenBSD
+2024-01-13 One reason why I love OpenBSD
+2024-04-01 KISS high-availability with OpenBSD
+2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage
+2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation
+
+E-Mail your comments to paul@nospam.buetow.org :-)
+
+Back to the main site
+

+Generated with Gemtexter 3.0.1-develop | +served by OpenBSD/relayd(8)+httpd(8) | +Site Mirrors +

+ + -- cgit v1.2.3