mudler
commented
2 years ago Hi! thanks a lot for the feedback, it's very appreciated!
I think the issue here is because in the cloud-init config there is both a vpn/c3os section and a manual start of k3s defined among the steps. If you don't need the vpn/c3os featureset, you can just drop the c3os/vpn block entirely and go manual.
viceversa, if you don't intend to manually configure k3s you can just use the c3os stanza that will configure k3s automatically, so no need to specify any k3s bit in the cloud-init.
TL;DR
or you go with:
c3os:
network_token: "...."
role: "master"
vpn:
# EdgeVPN environment options
DHCP: "false"
ADDRESS: "10.1.0.2/24"
stages:
initramfs:
- name: "Set user and password"
users:
c3os:
passwd: "c3os"or (note the network stage defined)
stages:
initramfs:
- name: "Set user and password"
users:
c3os:
passwd: "c3os"
network:
- if: '[ ! -f "/run/cos/recovery_mode" ]'
name: "Setup k3s"
environment_file: "/etc/sysconfig/k3s"
environment:
K3S_TOKEN: "..."
systemctl:
start:
- k3s
irishgordo
Hey there! I really have been enjoying getting started with c3os! I think it will serve as a great replacement for my 1U SuperMicro Server that was running K3OS.
I was leveraging the Manual Installation Portion - once I booted from the USB in GRUB2.
I had just shelled into the IP, SCP'd over a cloud_init file that looked like this:
Then just ran
sudo elemental install /dev/sda --cloud-init ./cloud_init.yaml. The install went great! And then once it was done, I rebooted, popp'd the USB drive out, shell'd into the box and snagged the kubeconfig from:sudo cat /etc/rancher/k3s/k3s.yaml. I was able to then on my workstation, hop on the kubectl with that --kubeconfig file. I installed cert-manager and rancher. It all was working like a charm. Got into the dashboard and everything. Reset the self-generated password. Powered it down for the night.When I booted it up this morning, I couldn't get kubectl to interact with the node. I hopp'd on and took a peek at the journalctl logs:
I'm thinking I just may have configured the cloud-init incorrectly? Should I have given a token that was alpha-numeric aside from just like ellipses "..."/"...."? Is it failing to start because of the:
No metadata/userdata found. Bye? Would this be something I could correct on the box somewhere in the/oem/path - or would it be easiest to blow it away and re-install it with a better cloud-init yaml config?Thanks again for all the hard work on this project! It's awesome! I definitely appreciate any info/feedback!