3 ms·
Out of curiosity what about a managed kube installation didnt work for your team?
by thinkingkong 7y ago
Out of curiosity what about a managed kube installation didnt work for your team?
- marcinzm 7y agoWe use EKS. It's been buggy especially in the networking plugin (CNI). For example, version 1.5.4 released at the end of September caused ip rules to randomly disappear and break things in mysterious ways. Anyone who launched a cluster during the 4 days it took them to change the default had to manually downgrade their version of CNI. Of course, EKS doesn't provide a way to control the version of components they add to new clusters. Or, as I remember, the master account that is given initial full access to the cluster.
- awinter-py 7y agoyup CNI
- marcinzm 7y agoMore broadly it just has so many rough edges and unfinished things. You can now do audit logging but you can't set an audit configuration so it logs everything (I think we had 200k events a day on a tiny cluster). You can tie service accounts to IAM roles but only if you cluster was created or upgraded after a certain date. You can't change or add subnets to the cluster without recreating it. Can't back a cluster or restore a cluster. Private load balancers require a non-standard configuration. EKS is still on 1.14 even though 1.17 is already out. The list goes on. Here's the current list of big and small issues people have with EKS: https://github.com/aws/containers-roadmap/issues?q=is%3Aopen+is%3Aissue+label%3AEKS https://github.com/aws/containers-roadmap/issues?q=is%3Aopen...