You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixtektoncd#8170
When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked
as failed immediately instead of waiting for it to timeout.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 2, 2024
…od OOM
fixtektoncd#8170
When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked
as failed immediately instead of waiting for it to timeout.
…od OOM
fixtektoncd#8170
When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked
as failed immediately instead of waiting for it to timeout.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 23, 2024
…od OOM
fixtektoncd#8170
When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked
as failed immediately instead of waiting for it to timeout.
Expected Behavior
After the Pod experiences an OOM, the TaskRun can fail promptly.
Actual Behavior
The TaskRun is in Running state for a long time.
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
This issue has been present in several recent LTS versions, including v0.53, v0.56, v0.59, and v0.62
The text was updated successfully, but these errors were encountered: