4 ms·
The problem wasn't in Kubernetes at all! The problem was in KIAM and the AWS Java SDK. It would be more accurate to criticize AWS's Kubernetes support. Both KI
by lacker 7y ago
The problem wasn't in Kubernetes at all! The problem was in KIAM and the AWS Java SDK.
It would be more accurate to criticize AWS's Kubernetes support. Both KIAM and the AWS Java SDK are specific to AWS.
- pojzon 7y agoWe found EKS to be really disappointing in comparison to Self hosted solution. Not only you simply cannot tweak extremely important kubelet configuration, you also cannot run real HA. Most of AWS implementation around EKS was simply terrible and outclassed by community driven projects. For me personally EKS is the same failed service as Elasticsearch Service. Good for low to medium size workloads but terrible for anything 1st world class.
- threeseed 7y agoWhy can't you run "real HA" with EKS ? It is after all running the control plane in multiple AZs.
- nielsole 7y agoAlso why can't you modify kubelet params? You are completely in charge of the nodes and can configure them freely.
- pojzon 7y agoThere are some cluster parameters you simply cannot change because api refuses or are not available (node cluster dependant parameters also). Example can be HPA downscale grace periods..
- pojzon 7y agoPlease check how aws recovers from lost master node. Its pretty straightforward from there.