The fsGroup field is a Pod security-context setting that assigns a supplemental group to every container and changes group ownership on mounted volume files. It helps a non-root process read protected volume content when the files initially belong to root. section 9.5.4
Letting Envoy read a private key
A secret volume contains example-com.key with mode 0640 and is initially owned by root:root. The Envoy process runs as user and group 101, so it cannot read the key. Add this to the Pod specification: fsGroup: 101. After recreating the Pod, the mounted files become owned by root:envoy, allowing Envoy to start and the Pod to reach Running status. section 9.5.4
fsGroup changes group ownership, not user ownership: mounted files can become owned by the selected group, but their user owner remains unchanged. section 9.5.4
