-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coschedule isolate-pipelinerun doesn't work #2318
Comments
Can you share what's the PipelineRun that is being generated by Trigger? Is feature flag configmap generated correctly? |
Hi, My tektonConfig: trigger:
chain:
This works if i used AWS EFS on my PVC and disable affinity roles. |
Expected Behavior
I have configured my tekton operator with:
I'm using the autoscaler on my node group on aws eks is using a ASG multi AZ. My trigger template has this configuration:
Actual Behavior
My pipelinerun has PVC and if I understand correctly the documentation, when we use coschedule isolate-pipelinerun, each pipelinerun should run in a different physical node, but it doesn't happen and retun this error:
Steps to Reproduce the Problem
Additional Info
Kubernetes version: 1.30
Output of
kubectl version
:Tekton Pipeline version: latest-v
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: