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
we need to destroy things very often in the reverse order in which they are installed. So for k3s or microk8s locally you can simply do a cleanup of the k8s server and then everything goes away BUT (and this is important) if you try to remove (say) an AWS EKS cluster that still has running apps and still has (especially) an active nginx and load balancer => it leaves an awful awful mess that takes a long time to clean up and leaves resources around that "cost money" !!!! So can I refer you top vNext beta mini-loop directory and the eks-setup tools in the vNext Beta that back out the apps and then back out the nginx and LB etc and then (and only then) do they remove infrastructure.
The text was updated successfully, but these errors were encountered:
we need to destroy things very often in the reverse order in which they are installed. So for k3s or microk8s locally you can simply do a cleanup of the k8s server and then everything goes away BUT (and this is important) if you try to remove (say) an AWS EKS cluster that still has running apps and still has (especially) an active nginx and load balancer => it leaves an awful awful mess that takes a long time to clean up and leaves resources around that "cost money" !!!! So can I refer you top vNext beta mini-loop directory and the eks-setup tools in the vNext Beta that back out the apps and then back out the nginx and LB etc and then (and only then) do they remove infrastructure.
The text was updated successfully, but these errors were encountered: