Brian Pribe
03/09/2024, 6:18 PM$KUBECONFIG path wasn't set to /etc/rancher/k3s/k3s.yaml. So I had to give the ec2-user permission to read the file (sudo chmod +r /etc/rancher/k3s/k3s.yaml) and then set the path to the file (sudo export KUBECONFIG=/etc/rancher/k3s/k3s.yaml). Now my k3s server is running. Now to debug the modules in the management.umh.app dashboard.
Edit: Damn shoulda seen this page sooner https://umh.docs.umh.app/docs/getstarted/managingthesystem/