[FLINK-31234] Add an option to redirect stdout/stderr for flink on kubernetes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.17.0
• Fix Version/s: 1.18.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: !huwh
• Reporter: !huwh
• Created: 27/Feb/23 06:51
• Updated: 12/Oct/24 08:02
• Resolved: 29/Jun/23 12:12

Description

Flink on Kubernetes does not support redirecting stdout/stderr to files. This is to allow users to get logs via "kubectl logs".

But for our internal scenario, we use a kubernetes user to submit all jobs to the k8s cluster and provide a platform for users to submit jobs. Users can't access kubernetes directly. so we need to display logs/stdout in flink webui.

Because the web ui retrieves the stdout file by filename, which has the same prefix as {taskmanager}.log (such as flink--kubernetes-taskmanager-0-my-first-flink-cluster-taskmanager-1-4.log). We can't support this with a simple custom image.

IMO, we should add an option to redirect stdout/stderr to files. When this setting is enabled.
1. flink-console.sh will redirect stdout/err to files.
2. avoid logs twices in the log file and the stdout file. we could do this by using ThresholdFilter (log4j and logback) with a system property.

Of course, this option is false by default.

Issue Links

• fixes: FLINK-31947 Enable stdout redirect in flink-console.sh
• is related to: FLINK-15792 Make Flink logs accessible via kubectl logs per default
• is related to: FLINK-17166 Modify the log4j-console.properties to also output logs into the files for WebUI
• links to: GitHub Pull Request #22138