1

Cronjob needs exit code to make the job successful or failed but with sidecar container an example the log container keep running and there is no exit code, even the job of the main container might run successfully the final state remain failed. There is any way to mitigate that issue ?! Thanks

Hamid Zorgani
  • 31
  • 3
  • Wait... log container... are you running a rsyslog/syslog sidecar? Sounds wrong... Can you share your CronJob definition? – SYN Jul 11 '21 at 16:12
  • There is a [long-standing Kubernetes issue](https://github.com/kubernetes/kubernetes/issues/25908) about this. If the sidecar is specifically Istio's proxy, [Terminate istio sidecar istio-proxy for a kubernetes job / cronjob](https://stackoverflow.com/questions/54921054/terminate-istio-sidecar-istio-proxy-for-a-kubernetes-job-cronjob) discusses Istio-specific solutions for it. – David Maze Jul 12 '21 at 10:33
  • Thanks @DavidMaze this is what exactly I'm looking for. – Hamid Zorgani Jul 12 '21 at 13:53
  • @DavidMaze could you possibly post your comment as an answer? – Jakub Siemaszko Jul 12 '21 at 16:04

1 Answers1

0

Having analyzed the comments it looks like it's a know issue and the fix can be found in this thread.

Jakub Siemaszko
  • 668
  • 3
  • 8