proxmox.md 1.9 KB
Notes on installing proxmox
Systems: EliteForums TH80 1TB drive in second slot
- Changes ACPI->AC Failure Resume to 'last state'
- Boot->Qiet Boot: Off
- Messed with boot order to something that seemed sane (USB first)
First system
I booted up to windows to see if I could get the Windows Key. Via powershell:
(Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey
3VJN2-PQTPX-BH3QG-HCRCC-J44C2
# Note, for future systems, you can run bash:
strings /sys/firmware/acpi/tables/MSDM
Inserted proxmox and saved and rebooted Plugged in network Install Proxmox VE (console) Got DHCP: 10.42.42.86 Target hard disk->Advanced Options, set "swap size" to 8, set "Maximum root volume size" to 128 Timezone to America/Detroit
Static IP (10.42.42.21) with 10.42.42.1 as DNS server
Take 2. Let it get a DHCP lease, then assigned a static mapping, rebooted and restarted installation.
Disable Enterprise Repositories
In UI, go to proxmox01, updates->repositories. DIsable both enterprise repos, and add both no-subscription repos.
apt update
apt install net-tools
Fix: Network didn't come up on next boot
vim /etc/network/interfaces
# Copy `iface enp1s0` line to `enp2s0`
# Add `enps20` to the bridge-ports
Reviewed settings, ran upgrade.
Second system wouldn't DHCP. Why?
Created 3x virtual machines on the local-lvm volume
k8s4, 5, and 6.
Installed
Updated
installed qemu-guest-agent
systemctl enable qemu-guest-agent
systemctl start qemu-guest-agent
Install microk8s
sudo snap install microk8s --classic --channel=1.27/stable
sudo usermod -a -G microk8s fdamstra
exit
# ssh back in
mkdir .kube
microk8s config > .kube/config
sudo chown -f -R fdamstra ~/.kube
edited /etc/hosts
10.42.42.204 k8s4.home.monkeybox.org k8s4
10.42.42.205 k8s5.home.monkeybox.org k8s5
10.42.42.206 k8s6.home.monkeybox.org k8s6
# on master
microk8s add-node
# cut and paste to the other 2