-
Notifications
You must be signed in to change notification settings - Fork 253
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
Delete Command for Pipeline, Resource, and Task Resources #193
Comments
/kind feature |
Could I take a remaining tasks (Pipeline, Task) ?? |
@16yuki0702 Go for it! |
@danielhelfand Thanks!! |
/assign |
@16yuki0702 Thanks for working on this, can you confirm you are working on all the delete resources? I.e: Task, TaskRun, Pipeline,PipelineRun Thanks, |
@chmouel yes, I'm working on all resources (Task, TaskRun, Pipeline, PipelineRun). Thanks !! |
I thinks this is completed. |
Yup, looks like delete is covered for every resource. Thanks, @16yuki0702! |
@danielhelfand Thank you for your confirming! |
This issue is a feature request for the ability to delete custom resource definitions for
tekton.dev
resources on a Kubernetes cluster. These resources include:Pipeline
Resource
Task
Currently, a user must use a second tool to delete these custom resources, such as
kubectl
oroc
. Being able to do this directly throughtkn
would help with having a user not have to go back and forth with another tool while usingtkn
.Expected Behavior
The delete command should remove a particular resource from a Kubernetes namespace.
Example with
Pipeline
:tkn pipeline delete pipeline_name
pipeline
to find and remove thepipeline
from the cluster namespaceAdditional Info
Since these features are already implemented in other Kubernetes tools, the question is how what should
tkn
overlap with for these other tools in terms of functionality versus leave to the other tools completely.In my opinion, I think it makes sense in this case to have the ability to also delete through
tkn
along with other Kubernetes tools.The text was updated successfully, but these errors were encountered: