Please help me understand this?

[BryanDollery]

I'm new to Tekton Pipelines, and it looks great so far. My local dev environment includes k3d and I install tekton pipelines using the operator without setting any extra flags. I'm developing my own specialized 'clone-repo' task. When I ran it I got this result (which I've fixed, I'm not asking for help with workspace bindings :) ):

completionTime: '2025-02-17T09:05:31Z'
conditions: - lastTransitionTime: '2025-02-17T09:05:31Z'
message: '[User error] workspace binding "robot" does not match any declared workspace'
reason: TaskRunValidationFailed
status: 'False'
type: Succeeded
podName: ''

What I'm asking is how I'm meant to read this? This is the error message thrown out by tekton when I've misconfigured something, right? Why is it there? I mean, why is it under "conditions"? Why is the type, "succeeded".

Help me understand? Is it just that the product is immature and things are still a bit raw? Or, is this meant to make sense to me?

TIA
Bryan

[afrittoli]

Hello @BryanDollery, thank you for trying Tekton.

About Conditions, they are a common paradigm to track the status of resources in Kubernetes, you can see them in Pods as well for instance. Each condition type tracks one aspect of the resource, and status and reason give you details about that.
Tekton uses a condition called Succeeded to track the final outcome of its resources.
In your case, this condition was:

• status: False, meaning it did not succeed
• reason: TaskRunValidationFailed, meaning that the TaskRun syntax or structure is invalid

You can find more about this in https://tekton.dev/docs/pipelines/taskruns/#monitoring-execution-status

About the specific error, it looks like there is a mismatch between the workspace declared in your Task and the one used in your TaskRun. Your TaskRun refers to a workspace called "robot" which is not defined in the Task.

HTH

[BryanDollery]

Oh, I see. It's a standard k8s condition and the the type is called "Succeeded". Well, even if that's a terrible name for a condition at least I understand it now. It's counter intuitive, but once explained it does make a twisted sort of sense :)

Thanks for the clarification. Much appreciated.