This message was deleted.
# k3s
a
This message was deleted.
r
I know RKE2 shows that, maybe k3s just.. doesn't?
c
there aren’t any pods for these things
https://docs.k3s.io/
Operation of all Kubernetes control plane components is encapsulated in a single binary and process.
they’re all running in the main k3s process, sharing the same memory and caches. That’s one of the things that makes K3s so much more memory efficient than other distros.
r
ahh nice okay
Any clean way to see the logs for those then?
Other than sshing in and tailing the k3s log?
c
look at the k3s logs. they’re all mixed together in there.
r
Got it, okay. Curiosity got the better of me when I was looking to move over to Cilium, maybe a good time to migrate over to RKE2 then.
c
Kubernetes uses klog which sets up a global logger. there’s no way to split out the component logs to separate files.
you should be able to use cilium on k3s just fine, if you disable flannel…
why would you need to switch to rke2?
r
Well mostly because I like having those separate pods, but partially also since I've already got a pretty heavily used cluster, migrating CNIs seems to be a huge pita.
c
The only significant difference between the two is that rke2 runs the components in static pods
r
Yeah, I do kinda want to have things be a little bit closer to k8s native
c
the rest of the code is directly imported from k3s
r
I like seeing the actual pods for it
I'm also unsure of loe to actually migrate cnis on a running cluster.
May end up doing a backup, spin up a new 'cluster' and then restore the etcd to a new master.
And have it start fresh.
And just stick to k3s
c
we don’t support switching CNIs after the cluster is up, no
r
yeah
I mean, nothing really supports that, so no throwing shade on k3s by any means
You have any examples of anyone using something like Promtail or some kind of log aggregator to pull from the k3s node logs and jam it into some kind of aggregation tool?
Maybe have to do privileged on the log collector pods.
c
not specifically. any of the normal tools that pull from journald should work.