redirect logs to the stdout in glusterd2

[Madhu-1]

In current GCS setup, all the logs are written to a file. we have to step inside the container and check the logs, if we redirect the logs to the stdout, we can use kubectl logs command to see glusterd2 logs.

[rishubhjain]

@Madhu-1 But this would be very specific to GCS, I think we can provide an option in the configuration file where one can mention whether the logs should be stored, either in file or redirected to stdout.

[JohnStrunk]

I think we can provide an option in the configuration file

Please make sure this is available via env or command line also. Managing config files is difficult in container environments.

[kshlm]

Even if we do provide an option, it will not be useful with the current containers which use systemd. As systemd is the first process in the container, the logs fetched by kubectl logs will be the systemd logs.