-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add tekton.dev/clusterTask in taskrun of clustertask #2390
Conversation
This will fix the issue of tekton.dev/task label getting added for taskrun created referencing clustetask Now it will be tekton.dev/clusterTask Add docs and fix test Fix tektoncd#2377
/cc @vdemeester @sbwsg |
/test pull-tekton-pipeline-integration-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/meow
/cc @sbwsg
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
In #2390 TaskRuns referencing ClusterTasks had their label changed from tekton.dev/task=<Name> to tekton.dev/clusterTask=<Name>. This is a backwards-incompatible change for teams relying on that original task label. This commit adds both labels to TaskRuns referencing ClusterTasks. We can then deprecate the tekton.dev/task= label on these TaskRuns in accordance with Pipelines' API deprecation policy.
This will fix the issue of tekton.dev/task label getting
added for taskrun created referencing clustetask
Now it will be tekton.dev/clusterTask
Add docs and fix test
Fix #2377
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes