i see that you can write manifests at

/var/lib/rancher/k3s/server/manifests/

. is there anything else like that for helm charts?

is there a way to pass the boot config without pointing to a url? and is there a way to specify the url at boot time, like in the kernel params?

Hi all, I was reading about some updates and I just wanted to confirm what I think I understand. I can install k3os from iso onto baremetal. I am prompted during the process including making a token if i want. Then, i can go to another baremetal machine and make it an agent and type in the token, ip address and it will work? I dont have to call up a github url if i dont want to during the install?

my client cert just expired. I tried getting a new one by just getting the one that kubectl on the master node is using, but that also says it's expired. how do I fix this?

Hi! I currently run into a few issues with k3os that I can’t seem to solve. A few questions regarding this: • is there someone or some support we could pay to resolve these issues? • the first issue: after a few days of a cluster node being active, I can see etcd logs complaining about requests taking too long (apply request took too long), which results in the node getting NotReady after a long time (hours) and k3s within k3os not recovering from the condition. After that happens the only two log messages are basically “compact tree index” and “finished scheduled compaction” but no other output (neither positive nor negative) ◦ restarting the node recovers the issue (but not very long) ◦ stopping k3s, deleting the etcd folder, restarting k3s recovers the issue (not sure if it will fail again, since this was the last thing I tried) ◦ I can see a LOT of connections to port 2379 although this cluster currently has only 4 nodes (should have 5, but one is not available right now) ◦ the issue happens randomly on arbitrary nodes (no logic to see right now) ◦ the servers are not fully loaded, are bare metal and should be fast enough not to run into etcd performance issues ◦ I’m running k3OS v0.22.2-k3s2r0 (unfortunately, the cluster was incorrectly set up) • second issue: I cannot see etcd metrics (curl http://localhost:2379/metrics returns an empty response) ◦ this happens on all cluster nodes

Does anyone know if there’s a k3os release coming anytime soon w/ newer k3s? Seems like the pre-release has been out there for a while, and even that has an old(er) version of k3s

hasn’t even been any commits in 4 months — is k3os still active / part of the future with rancher ?

Is there any way to install rclone on the host? There's two projects for using rclone in kubernetes, but one relies on rclone being on the host, and the other can't handle anything that uses a login token that changes, since it uses a secret for storing the config and it can't be changed by the csi plugin so I'd have to basically rewrite the secret manually twice a day... And that's not happening >_<

When running the 1.19 variant of k3os to rotate my certs do I need to restart all masters or one?

Is K3os really dead?

yes.

I really loved k3os

what is the alternative now?

@bland-area-30120 has left the channel

hey y'all - is there anyway to load the installation config (k3os.install.config_url) from CD-ROM (cloud init) instead of a URL?

i'm trying to use terraform to provision these and I need to be able to modify the hostname for each and so a static file won't work