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
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