Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.2.1
Opened: Apr 30, 2024 Severity: 3-Major
When a Kubernetes pod is restarted, the logs from the previously running pod are lost.
QkView does not have logs from before the pod was restarted The new logs generated after the restart will not contain information about the cause of the restart.
-- Viewing logs for a Kubernetes pod what was restarted -- You wish to review log messages occurred before the pod was restarted
To understand why a pod was restarted, you can get CM logs that have all comprehensive feature-level logs which provide a user with all of the previous/current CM activities and all information about what might have caused the pod to restart. You can follow the instruction to generate a CM qkview file and uplad it to F5 iHealth from this link: https://clouddocs.f5.com/bigip-next/latest/support/cm_qkview_script.html Once you upload the generated CM qkview to iHealth, 1. click on the entry that you have just uploaded to iHealth webpage. 2. Go to "Files" tab on the left side of your screen to see the whole file tree. 3. Go to all -> host-qkview -> filesystem -> var -> log -> application and download the latest application log (application.0.log)
None