This message was deleted.

the kubelet tells the container runtime where to put the logs. kubelet makes the directory, and when it runs a container, sets the path for that container’s logs to a file in that directory. the container runtime creates the log when the container starts.

The question is can the permission/ownership of the logs be changed?

There's some weird conflation in that issue about inside/outside of the container.

I don’t think so

I’m talking about the contents of the stdout/stderr output of the process, how to access that (i.e. podsandbox field

log_directory

and containerconfig field

log_path

in the CRI protocol).

This threw me off:

The logs inside the container (the running processes).