Why are the file systems for worker nodes changed to read-only?

Classic infrastructure

You might see one of the following symptoms {: #stuck_creating_state}:

• When you run kubectl get pods -o wide, you see that multiple pods that are running on the same worker node are stuck in the ContainerCreating state.
• When you run a kubectl describe command, you see the following error in the Events section: MountVolume.SetUp failed for volume ... read-only file system.

The file system on the worker node is read-only.

Back up your data and reload your worker node.

1. Back up any data that might be stored on the worker node or in your containers.
2. For a short-term fix to the existing worker node, reload the worker node.

   ibmcloud ks worker reload --cluster <cluster_name> --worker <worker_ID>
   

For a long-term fix, update the flavor of your worker pool.