[ENG-2583] Pipe K8s logs back into the Aqueduct executor
kenxu95 opened this issue · comments
This will make it a lot easier to debug K8s issues, especially on github actions where we have access to the executor logs, but the cluster has been torn down.
We can probably use the golang K8s API. Retrieve the log on operator termination and log to the appropriate surface (server logs for preview, workflow log file for published flows).
From SyncLinear.com | ENG-2583
I just changed it. In talking with Kenny, 2661 was prioritized over this. I should have moved this out of 2.9 release on Friday.
our comments crossed mid-air :-)
seems like you added a release label from the past (Jan) mistakenly (the date in paranthesis should be helpful).
Bit confused then as to why this task you have not started on is tagged for 2.9 release (cut-off today) and the task you are working ENG-2661 on is tagged for 2.10 release (one week later)?
@jpurusho65 are you currently working on this?
FYI: the process is to update status to "In Progress" once you start working on a task.
Will assign to Jerome. Taking it for now to track.