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

delete in dashboard does not cascade #980

Closed
puja108 opened this issue Jun 30, 2016 · 14 comments
Closed

delete in dashboard does not cascade #980

puja108 opened this issue Jun 30, 2016 · 14 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@puja108
Copy link
Member

puja108 commented Jun 30, 2016

Issue details

When deleting a deployment/rc/rs in dashboard the delete does not cascade like it does with kubectl delete. I'd say the cascading should be the expected behavior as it is also the default with kubectl.

Environment
Dashboard version: 1.1.0
Kubernetes version: 1.2.5
Operating system:
Node.js version:
Go version:
Steps to reproduce
  1. Delete any deployment, rc, or rs
Observed result

The delete does not cascade to resources managed by the deleted resource.

Expected result

Cascading delete like with kubectl delete (default behavior), i.e. deployment->rs->pods; rs->pods; rc->pods

Comments
@floreks
Copy link
Member

floreks commented Jun 30, 2016

I've encountered same issue lately. We have to rethink our generic approach to delete, because it leaves orphaned resources on the cluster.

cc @bryk

@floreks floreks added kind/bug Categorizes issue or PR as related to a bug. priority/P1 labels Jun 30, 2016
@bryk
Copy link
Contributor

bryk commented Jun 30, 2016

I definitely agree. We need to wait until this is implemented on the server side: kubernetes/kubernetes#19054

Otherwise, it is us duplicating kubectl and apiserver work.

Thoughts?

@floreks
Copy link
Member

floreks commented Jun 30, 2016

Nice. Didn't know about that. We should definitely wait for kubernetes to get this feature.

@puja108
Copy link
Member Author

puja108 commented Jun 30, 2016

Same here, looks like we should wait then, also good discussion about what the default should be. For me the default for UI should be same as for kubectl to have a coherent UX across CLI and UI.

@floreks
Copy link
Member

floreks commented Jun 30, 2016

For me the default for UI should be same as for kubectl to have a coherent UX across CLI and UI.

That's our goal :)

@bgrant0607
Copy link
Member

cc @caesarxuchao

@caesarxuchao
Copy link
Member

In the upcoming 1.4 release, server-side cascading deletion of rc and rs is possible, dashboard just needs to send to apiserver a deletion request with DeleteOptions.OrphanDependents=false.

We will work on the other use cases in 1.5.

@floreks
Copy link
Member

floreks commented Aug 30, 2016

Great! We should support this.

cc @bryk @maciaszczykm

@bryk bryk added this to the 1.4 milestone Aug 30, 2016
@bryk
Copy link
Contributor

bryk commented Aug 30, 2016

@caesarxuchao Cool, thanks.

Will we get cascade delete for free for future use cases when we just send DeleteOptions.OrphanDependents=false with all delete requests?

@bryk bryk self-assigned this Aug 30, 2016
bryk added a commit to bryk/dashboard that referenced this issue Aug 30, 2016
Plus remove unused RC delete code.

Re kubernetes#980
@caesarxuchao
Copy link
Member

caesarxuchao commented Aug 30, 2016

@bryk what are the future use cases you have in mind? We will support cascading deletion for Deployment in the future.

@puja108
Copy link
Member Author

puja108 commented Aug 31, 2016

Can't test right now, but Jobs would be good.

On a sidenote: Does deletion of namespaces (I'd guess that always incl all their resources) work in Dashboard?

@bryk
Copy link
Contributor

bryk commented Aug 31, 2016

@puja108 We dont (yet) support deletion/modification of cluster admin resources. It is challenging, as you already noticed, so we want to tackle this only when we have time to do this right.

@bryk
Copy link
Contributor

bryk commented Aug 31, 2016

@caesarxuchao

what are the future use cases you have in mind? We will support cascading deletion for Deployment in the future.

Yes, cases like cascade delete for Deployments or Namespaces.

floreks pushed a commit that referenced this issue Aug 31, 2016
Plus remove unused RC delete code.

Re #980
joe2far pushed a commit to ammeon/dashboard that referenced this issue Sep 5, 2016
@maciaszczykm maciaszczykm removed this from the 1.4 milestone Mar 8, 2017
@maciaszczykm
Copy link
Member

Will track it from #1570.

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

6 participants