Skip to content
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

StepActions - Cluster resolver Tasks using StepActions look for the StepAction in the namespace of the calling Pipeline and not the Task #8380

Open
AverageMarcus opened this issue Nov 11, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@AverageMarcus
Copy link
Contributor

Expected Behavior

I have a Pipeline in namespace-a which includes a Task using the Cluster resolver to make use of a Task in namespace-b. The Task in namespace-b includes a StepAction using a name reference. The StepAction is also in namespace-b. I expect the Pipeline to successfully load the Task from the other namespace and correctly look up the associated StepAction.

Actual Behavior

The Pipeline Task fails with TaskRunResolutionFailed as it attempts to load the StepAction from the same namespace as the Pipeline (namespace-a) rather than the namespace of the referenced Task (namespace-b)

Steps to Reproduce the Problem

  1. Create a StepAction and a Task that references it using a ref name in the same namespace as each other.
  2. Create a Pipeline in a different namespace and use the cluster resolver to include the Task from the other namespace.
  3. Run the Pipeline and observe the failure

Additional Info

  • Kubernetes version:

    Output of kubectl version:

Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.9
  • 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}'

Client version: 0.37.0
Pipeline version: v0.65.1
Triggers version: v0.30.0
Dashboard version: v0.52.0
@AverageMarcus AverageMarcus added the kind/bug Categorizes issue or PR as related to a bug. label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant