You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cncf-kubernetes provider, KubernetesPodOperator provides get_logs and log_containers arguments to support pulling logs generated from created Kubernetes pod into task logs, and these arguments are also available in KubernetesJobOperator through class inheritance.
However, KubernetesJobOperator does not implement logs pulling mechanism, so user has no way to transfer pod logs from the created job to task logs within this operator.
Use case/motivation
Supports get_logs and log_containers settings in KubernetesJobOperator when wait_until_job_complete is enabled (otherwise it's user's responsibility to manage logs/output generated from the job).
We can take similar approach used in KubernetesPodOperator to regularly fetch pod logs under the created job.
Description
In
cncf-kubernetes
provider,KubernetesPodOperator
providesget_logs
andlog_containers
arguments to support pulling logs generated from created Kubernetes pod into task logs, and these arguments are also available inKubernetesJobOperator
through class inheritance.However,
KubernetesJobOperator
does not implement logs pulling mechanism, so user has no way to transfer pod logs from the created job to task logs within this operator.Use case/motivation
Supports
get_logs
andlog_containers
settings inKubernetesJobOperator
whenwait_until_job_complete
is enabled (otherwise it's user's responsibility to manage logs/output generated from the job).We can take similar approach used in
KubernetesPodOperator
to regularly fetch pod logs under the created job.Related issues
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: