Results 5 comments of shadowinlife

Any guys resolved this? I catch same issue with spark 3.2.0 on k8s

With a `sidecar` or just a `jvm thread` collect logs of pod and append to s3 files is a alternative for this scope. And worked well in my production k8s....

temporary close for need more tests on my k8s environment

Thanks, then I think I can created a factory method for `manager starter` action. Then for most `spark-operator` user, the default `informer` not changed. For some user need solutions like...