No scheduler logs when deployed to k8s

[andygrove]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
According to the user guide, it should be possible to see scheduler logs:

$ kubectl logs ballista-scheduler-0
[2021-02-19T00:24:01Z INFO  scheduler] Ballista v0.7.0 Scheduler listening on 0.0.0.0:50050
[2021-02-19T00:24:16Z INFO  ballista::scheduler] Received register_executor request for ExecutorMetadata { id: "b5e81711-1c5c-46ec-8522-d8b359793188", host: "10.1.23.149", port: 50051 }
[2021-02-19T00:24:17Z INFO  ballista::scheduler] Received register_executor request for ExecutorMetadata { id: "816e4502-a876-4ed8-b33f-86d243dcf63f", host: "10.1.23.150", port: 50051 }

However, I just tried this, and there is no logging.

We should update the user guide to explain how to enable logging or maybe enable it in the provided yaml.

Describe the solution you'd like
None

Describe alternatives you've considered
None

Additional context
None

[avantgardnerio]

Likely need:

spec:
  containers:
  - name: envar-demo-container
    image: gcr.io/google-samples/node-hello:1.0
    env:
    - name: RUST_LOG
      value: "debug"
      ```

[mingmwang]

I think the log was saved to files, it is not output to stdout anymore. @Ted-Jiang

[Ted-Jiang]

I think the log was saved to files, it is not output to stdout anymore. @Ted-Jiang

Thanks for remind me this, I found i miss the declaration of std-output in tokio-tracing 😂
I will fix this