all our existing NFS PVCs have reset the UID and GID from all files and directories to 99 instead of the UID of the container user.
This leads to the issue, that existing files and not be written from the container.
New files however, have the correct UID and GID
Openshift is using arbitrary user ids and our deployment dont use any security context to change mounted pvcs permssions.
What could have caused this?
Kind regrards
Philipp
Setup:
Openshift 4.10 with kubernetes v1.23.12+8a6bfe4
Red Hat Enterprise Linux CoreOS 410
Trident 22.01.0
Hi,
all our existing NFS PVCs have reset the UID and GID from all files and directories to 99 instead of the UID of the container user. This leads to the issue, that existing files and not be written from the container.
New files however, have the correct UID and GID
Openshift is using arbitrary user ids and our deployment dont use any security context to change mounted pvcs permssions.
What could have caused this? Kind regrards Philipp
Setup: Openshift 4.10 with kubernetes v1.23.12+8a6bfe4 Red Hat Enterprise Linux CoreOS 410 Trident 22.01.0
Storageclass:
trident Backend: