Wrong runAsUser UID for pulp_web container

We have updated our Kubernetes cluster to a recent version (1.33). After the update, the pulp-web container can no longer start. The error message is:

2025/07/27 05:50:07 [emerg] 8#8: mkdir() "/var/cache/nginx/client_temp" failed (13: Permission denied)
nginx: [emerg] mkdir() "/var/cache/nginx/client_temp" failed (13: Permission denied)

The operator starts the container with:

runAsUser: 700
fsGroup: 700

However, in the pulp_web image, the UID 101 is used for the nginx user.
I suspect this is the reason for the "permission denied" error, but I'm not 100% sure.

Is there an "easy" way to implement a workaround for this?
Or is there perhaps a way to override UID 700 with 101?

Thank you very much for your response.

Update:

When i use fsGroup: 0 than i can start teh pulp-web container.

Start with the operator configuration for the pulp_web container and compare its runAsUser and fsGroup settings with the image’s nginx UID 101. Reproduce the startup failure on Kubernetes 1.33 using the reported security context, then verify that the container starts without the nginx permission-denied error under the supported configuration.