Guy Harel
06/10/2024, 12:29 PMKetan (kumare3)
Ketan (kumare3)
Guy Harel
06/10/2024, 2:28 PMKetan (kumare3)
Guy Harel
06/10/2024, 2:31 PMLimits:
cpu: 4
memory: 28Gi
Requests:
cpu: 2
memory: 28Gi
Guy Harel
06/10/2024, 2:35 PMKetan (kumare3)
Ketan (kumare3)
Ketan (kumare3)
Ketan (kumare3)
Guy Harel
06/13/2024, 7:30 AMKetan (kumare3)
Guy Harel
06/13/2024, 2:43 PMDavid Espejo (he/him)
06/13/2024, 9:02 PMRegarding inject-finalizer, I see that we did in fact have this set to "true", if we turn it off, what are the implications?I think it's fine to leave it
True
especially if you need to handle high load in your cluster. It basically enables a tighter control on Pod's lifecycle, preventing Pods from being deleted until Flyte explicitly removes the finalizer. The error message you're getting is not the typical one when those situations happen though. Here is the worker who seems to find an stale ResourceVersion and then it's prevented from writing changes to the resource. There are ways to handle this, some of them covered in this page
As per the 503
error getting the token, not sure if it refers to the ID Token that OIDC returns, which comes from your IdP in this case but it's a sign of high load somewhereKetan (kumare3)