Google Professional Cloud Developer
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
You recently deployed an application to GKE with Pods writing files to a Compute Engine persistent disk. You created a PersistentVolumeClaim (PVC) and PersistentVolume (PV) in Kubernetes for the disk, and referenced the PVC in the deployment manifest.
After expanding the persistent disk due to near-full capacity, you notice the disk expansion isn't reflected in the container's file system when inspecting a Pod. What steps should you take to resolve this?
Explanation:
To resolve the issue where the disk expansion is not visible in the container file system after expanding a Compute Engine persistent disk used by a GKE Pod, you need to update the PersistentVolume (PV) object's capacity to match the new size of the persistent disk. This is done by setting the spec.capacity.storage value of the PV object (option A). After updating the PV, the PersistentVolumeClaim (PVC) bound to it will recognize the new capacity. However, the Pods need to be restarted to remount the volume and see the expanded filesystem. While option B suggests recreating the Pods, which is a necessary step, the primary action required is updating the PV's capacity. Therefore, the correct answer is to update the PV's capacity as described in option A.