3 ms·
DigitalOcean also cordons Nodes for no reason at random times. Currently moving to EKS exactly for this reason
by bithavoc 4y ago
DigitalOcean also cordons Nodes for no reason at random times. Currently moving to EKS exactly for this reason
- atmosx 4y agoCan you share more details please? How did you find out it was DO, did you open a support ticket?
- bithavoc 4y agowell, I'm the only one with access to the cluster and I didn't do it, with Lens IDE I barely check the Nodes tab, I checked the Nodes because I noticed no app pods were scheduling in such node and I found it cordoned.
- taspeotis 4y agoIn late 2021 we had EKS nodes shit the bed for no apparent reason. Max out CPU and couldn't SSH in. They'd get recreated eventually by EC2 (multiple hours) despite being tainted in k8s pretty quickly. We ran with N+2 nodes to deal with it. After dutifully updating EKS releases and AMIs it seems to have fixed itself last year. EKS seems to be fine generally, but it would be nice if they didn't release new AMIs with missing commits?? [1] and especially [2] [1] https://github.com/aws/containers-roadmap/issues/319 https://github.com/aws/containers-roadmap/issues/319 [2] https://github.com/awslabs/amazon-eks-ami/issues/278#issuecomment-498693960 https://github.com/awslabs/amazon-eks-ami/issues/278#issueco...