You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It’s common to delete multiple objects defined in a manifest, rather than only removing the Deployment, e.g. kubectl delete -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.5.0/components.yaml
Because a manifest can create more than what can be managed in Kubernetes (cluster objects, Role, RoleBindings, ServiceAccounts…), when removing an application from Portainer this will leave some orphaned objects inside the cluster.
Describe the solution you'd like
When removing a stack from the Stacks tab, remove all associated workloads.
But when deleting the Deployments from the applications list, it may leave workloads behind (like services etc).
So for it to work correctly (i.e. leave nothing behind), the user has to delete the Stack.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It’s common to delete multiple objects defined in a manifest, rather than only removing the Deployment, e.g.
kubectl delete -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.5.0/components.yaml
Because a manifest can create more than what can be managed in Kubernetes (cluster objects, Role, RoleBindings, ServiceAccounts…), when removing an application from Portainer this will leave some orphaned objects inside the cluster.
Describe the solution you'd like
![image](https://user-images.githubusercontent.com/77944876/134443397-279f725f-b585-47ff-b383-ef04d651c992.png)
When removing a stack from the Stacks tab, remove all associated workloads.
But when deleting the Deployments from the applications list, it may leave workloads behind (like services etc).
So for it to work correctly (i.e. leave nothing behind), the user has to delete the Stack.
The text was updated successfully, but these errors were encountered: