Menu

EKS 1.31 extended support ends Nov 26. On 1.32, ReadWriteOncePod volumes change file ownership.
📰

EKS 1.31 extended support ends Nov 26. On 1.32, ReadWriteOncePod volumes change file ownership.

DEV Community: kubernetes·Silpa Nallagopula·6 days ago
#QP6itRyd
Reading 0:00
15s threshold

EKS 1.31 leaves extended support on November 26, 2026. After that date AWS upgrades the control plane to 1.32 for you, with no notice beforehand. So if you still have a 1.31 cluster, you're about to do the 1.31 to 1.32 hop whether you planned it or not.

Most people prepare for a hop by scanning for removed APIs. That scan comes back clean for this one. It still misses a change I think is worth ten minutes.

The 1.32 changelog has this line:

Apply fsGroup policy for ReadWriteOncePod volumes.

That's the whole entry. Here is what it means. If a pod sets securityContext.fsGroup and mounts a ReadWriteOncePod volume, the files on that volume get re-owned to the fsGroup the first time the pod mounts it after the upgrade. ReadWriteOnce volumes already worked this way. ReadWriteOncePod ones didn't.

For most apps that's harmless. It matters in two cases. One is an app that depends on the ownership its files had before.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.