-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENG-2583] Pipe K8s logs back into the Aqueduct executor #1238
Comments
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)? |
No Suresh, I haven't started on this yet. I changed the ENG-2661 to progress. |
@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. |
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
The text was updated successfully, but these errors were encountered: