kube-logging: rke2-logs-{server,agent}-host-tailer CrashLoopBackOff
Observed pods: ``` kube-logging/rke2-logs-server-host-tailer-* CrashLoopBackOff kube-logging/rke2-logs-agent-host-tailer-* CrashLoopBackOff kube-logging/rke2-logs-kubelet-host-tailer-* Running (file tailer) ``` HostTailer CR shows systemdTailer configured with: ``` systemdFilter: rke2-server.service (or rke2-agent.service) path: /var/log/journal ``` On SLES15, `/var/log/journal` is not created by default unless persistent journald storage is enabled; only `/run/log/journal` is typically present. Result: Fluent Bit starts, tries to read journald from `/var/log/journal`, directory does not exist, container exits immediately → CrashLoopBackOff. Logs are often empty; only restart/backoff events are visible.
issue