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
Hello, at present, I am using the tekton 0.7.0 version, after running for half a year, I found that when the pod CPU of tekton-pipelines-controller reaches 70% and the memory reaches more than 50%, there will be a situation where the pod of the build task cannot be generated, and it is a probabilistic problem, and it is not completely impossible to generate the build task, the service will return to normal after the pod of the controller is restarted, and it is initially suspected that it is a problem of coroutine leakage, I guess you should have fixed this problem.,I want to know what the root cause of this problem is.,Please let me know.,Thank you.
Additional Info
Kubernetes version:
Output of kubectl version:
Client Version: v1.29.1
Server Version: v1.24.6-aliyun.1
Tekton Pipeline version:
Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
This label is not visible in the pod's labels for the time being
labels:
app: tekton-pipelines-controller
app.kubernetes.io/component: controller
app.kubernetes.io/name: tekton-pipelines
pod-template-hash: 6fdbdf4d45
The text was updated successfully, but these errors were encountered:
@fjzcxs are you sure you are using 0.7.0 version of tektoncd/pipelines ?
The current version is 0.66.0. The version 0.7.0 would be ~5 years old (2019), so very very old, not supported and would have get a lot of improvement over time.
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Hello, at present, I am using the tekton 0.7.0 version, after running for half a year, I found that when the pod CPU of tekton-pipelines-controller reaches 70% and the memory reaches more than 50%, there will be a situation where the pod of the build task cannot be generated, and it is a probabilistic problem, and it is not completely impossible to generate the build task, the service will return to normal after the pod of the controller is restarted, and it is initially suspected that it is a problem of coroutine leakage, I guess you should have fixed this problem.,I want to know what the root cause of this problem is.,Please let me know.,Thank you.
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}'
The text was updated successfully, but these errors were encountered: