Issue with Pods not being killed

Summary

Pods are not being killed as expected, causing an issue. Need to investigate why.


Question

what is happening with the pods? shouldn’t they be killed?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["pods", "killed", "issue"]

the completed ones will be removed by the pod-sweeper. you can check out the script here: https://github.com/airbytehq/airbyte-platform/blob/013c3980494d16ad912dc6f0c97c1fe1ac16a083/charts/airbyte-pod-sweeper/templates/configmap.yaml
The times are configurable in the helm chart: https://github.com/airbytehq/airbyte-platform/blob/013c3980494d16ad912dc6f0c97c1fe1ac16a083/charts/airbyte-pod-sweeper/values.yaml#L97-L108

<@U03FNJGED7D> would you know why some of my syncs are stuck… it has been 5 hours but I know there is not a lot of data with the sync

I only can see that the workload is claimed. Is there a way to inspect the workload itself for more details?

your oldest destination was created 10 minutes ago, not 5 hours ago, so I don’t think any syncs have been trying to run for that long

here is the log maybe I am missing something:

it is still running btw

I ran the destination check manually 10 mins ago

any thoughts <@U03FNJGED7D>?

no, sorry. I haven’t updated to the platform version in a while, so that’s not something I’m familiar with

no worries thanks for your thoughts!