Cascading Deployment Removal
See original GitHub issueWhen calling delete_namespaced_deployment
, even with orphaned_dependents
(which doesn’t mean I think it means), only the deployment object itself gets removed. This means you’ve got the ReplicaSet and 1 or more Pods still running.
Between garbage collection and ReplicaSet references to the Deployment that created it, there still doesn’t seem to be a way to have a delete
cascade properly.
Kinda wondering how others are solving the problem and if maybe there needs to be more development in this area either here or upstream. Merely trying to provide a reliable removal function in my application…
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Use Cascading Deletion in a Cluster - Kubernetes
You can delete objects using foreground cascading deletion using kubectl or the Kubernetes API. Using kubectl. Run the following command:.
Read more >Introduce cascading deletion · Issue #1570 - GitHub
@kargakis I just tried to cascade-delete a deployment created on 1.6 cluster. It deleted replica sets, but pods stayed there.
Read more >App Deletion - Argo CD - Declarative GitOps CD for Kubernetes
Apps can be deleted with or without a cascade option. A cascade delete, deletes both the app and its resources, rather than only...
Read more >Removing cascade deletion in the production environment to ...
When records are deleted in the staging environment for a database table that contains a cascade-delete foreign key relationship with another table and...
Read more >Cascading deletion does not work according to the ...
For instance, if you delete a Deployment object, but ReplicaSet which depends on the Deployment would not be removed automatically.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
What version of Kubernetes are you running? This feature is only supported since 1.6.0
On Jun 13, 2017 17:38, “Konrad Djimeli” notifications@github.com wrote:
No, the replicaset not deleted.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes-incubator/client-python/issues/162#issuecomment-308175921, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmuSQCCC11xFAW8cPxCf-2b-lYuYSELks5sDrsPgaJpZM4MsaC8 .
I’ve tried it, working fine for my application, at least the new options I needed in v1_delete_options.py are working fine.