Provide Information On Remote Logging

**What I'd like:**
We currently use Fluent-bit, and Promtail for remote logging. Fluent-bit *was* configured using this guide: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-logs-FluentBit.html but since we switched to Bottle Rocket, we lost the host logs.

Same with Promtail, we ship all the container logs etc to Loki, but again, we are not getting kubelet logs etc.

Just some basic information on how to get this working would be amazing. From Promtail/Fluent-bits perspective, we just really need to know which volumes to mount on the host, and if they are files we `tail` or `systemd` logging.

Running Bottle Rocket has left a huge gap in what information we are able to use to troubleshoot, since we are hitting an issue where a node goes notready, and the kubelet dies, and AWS SSM access stops, we are basically only left with deleting the node.

Start by locating the website's existing troubleshooting or logging documentation, then review the AWS Fluent Bit guide alongside the Promtail, Loki, kubelet, and SSM context in this issue. Document which host volumes remote collectors need and whether the relevant logs are files or systemd logs, with enough guidance to investigate a not-ready node and stopped kubelet.

Written by the indexing model from the issue text.