Open
Description
What were you trying to accomplish?
Deleting EKS cluster provisioned with addons.
What happened?
When deleting the cluster first step is cordoning the nodes. EBS addon is running controller replica and is blocking cordoning of the nodes. We should probably be removing the addons first to ensure only workloads are running before cordoning.
How to reproduce it?
Provision EKS cluster with a addon (EBS). Then delete is using eksctl delete cluster -f config.yaml
Logs
2023-02-13 14:36:56 [ℹ] deleting EKS cluster "mb"
2023-02-13 14:36:57 [ℹ] will drain 0 unmanaged nodegroup(s) in cluster "mb"
2023-02-13 14:36:57 [ℹ] starting parallel draining, max in-flight of 1
2023-02-13 14:36:58 [ℹ] cordon node "ip-192-168-29-32.eu-west-1.compute.internal"
2023-02-13 14:36:58 [ℹ] cordon node "ip-192-168-46-245.eu-west-1.compute.internal"
2023-02-13 14:36:58 [ℹ] cordon node "ip-192-168-92-221.eu-west-1.compute.internal"
2023-02-13 14:38:12 [!] 1 pods are unevictable from node ip-192-168-29-32.eu-west-1.compute.internal
2023-02-13 14:39:14 [!] 1 pods are unevictable from node ip-192-168-29-32.eu-west-1.compute.internal
2023-02-13 14:40:16 [!] 1 pods are unevictable from node ip-192-168-29-32.eu-west-1.compute.internal
2023-02-13 14:41:18 [!] 1 pods are unevictable from node ip-192-168-29-32.eu-west-1.compute.internal
2023-02-13 14:42:20 [!] 1 pods are unevictable from node ip-192-168-29-32.eu-west-1.compute.internal
Anything else we need to know?
Versions
$ eksctl info
eksctl version: 0.129.0
kubectl version: v1.26.1
OS: linux