[MZC-CSC]

What's Changed

README: keep the inode when editing the running IAM nginx.conf (504 Known Issues)

The Known Issues step for raising proxy_read_timeout on a running installation used sed -i followed by nginx -s reload. The generated nginx.conf is bind-mounted into mc-iam-manager-nginx as a single file (./container-volume/mc-iam-manager/nginx/nginx.conf:/etc/nginx/nginx.conf:ro). sed -i replaces the file with a new inode, so the container keeps reading the old content and the reload has no effect.

• README.md / README_kr.md (Known Issues, IAM nginx 504):
  • Write the edited copy to a temporary file and copy it back with cat > so the file keeps its inode, then run nginx -t && nginx -s reload
  • Add a step to check the value nginx is actually using: nginx -T | grep proxy_read_timeout
  • Add a note explaining the single-file bind mount and that if the file was already edited with sed -i (or an editor that replaces the file), docker restart mc-iam-manager-nginx is needed instead of reload
• Documentation only; no changes to templates, compose files, or images

Verified locally with nginx:1.25-alpine and a single-file bind mount: sed -i + reload kept the old value, docker restart applied the new value, and cat > + reload applied the new value.