Answer-first summary for fast verification
Answer: Check the container/ephemeral_storage/used_bytes metric by using Metrics Explorer.
To identify which Pods are causing the DiskPressure node condition without having execute access to workloads and nodes, the best approach is to use Google Cloud's monitoring tools. Option A suggests checking the node/ephemeral_storage/used_bytes metric, which provides information about the ephemeral storage usage at the node level but does not pinpoint specific Pods. Option B, checking the container/ephemeral_storage/used_bytes metric, is more precise as it provides ephemeral storage usage at the container level, which can help identify the specific Pods causing the issue. Options C and D involve using commands that require execute access to the nodes, which the scenario explicitly states you do not have. Therefore, the correct answer is B, as it allows you to identify the problematic Pods without needing direct access to the nodes.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
How can you identify which Pods are causing DiskPressure node conditions in your GKE cluster when you lack execute access to workloads and nodes, given that several applications rely on ephemeral volumes?
A
Check the node/ephemeral_storage/used_bytes metric by using Metrics Explorer.
B
Check the container/ephemeral_storage/used_bytes metric by using Metrics Explorer.
C
Locate all the Pods with emptyDir volumes. Use the df -h command to measure volume disk usage.
D
Locate all the Pods with emptyDir volumes. Use the df -sh * command to measure volume disk usage.