When many pods write/read to the same shared folder, you can’t see the I/O pressure using kubectl top pod alone — that only shows CPU/memory, not disk I/O per shared volume.
The "top" directory is the entry point for every user accessing the KShared drive. It acts as the digital lobby of your organization. kshared folder top
have reported confusion over this exact behaviour. In some versions, newly created subfolders do not automatically inherit the parent’s sharing settings, leading to complaints that “some subfolders are not seen by the people that have access”. This is not a bug; it is often a result of permission inheritance being broken at some point. The solution is to manually share the subfolders or to reset inheritance from the top level. When many pods write/read to the same shared
Hardware for Linux