Been waiting for this for... 7 months now since its announcement at ReInvent?<p>My initial impressions are very negative. What even is the <i>point</i> of this? The clusters themselves do nothing, they're just a control plane you pay $144/month for. You need to add nodes from CloudFormation? Is there any integration at all with CodeBuild/CodeDeploy/CodePipeline? No mention anywhere of Ingress... I sure hope that's built in, but from what I'm reading it isn't? What was Amazon thinking by releasing this so unfinished?
I find Amazon’s attitude towards the whole Kubernetes lukewarm at best. It seems they really wanted ECS to be the killer container service on AWS but when k8s took over the mindshare they reluctantly added Fargate and EKS at slow speed and with an underwhelming product.<p>We worked with both AWS container solutions and GKE and find GKE far superior. We had to build Skycap as deployment solution for our applications on top of it but the end result is an amazingly simple system delivering HA and robustness we never could have imagined with any other solution as easily.
> You pay $0.20 per hour for the EKS Control Plane, and usual EC2, EBS, and Load Balancing prices for resources that run in your account<p>Objectively that's not bad for HA masters in separate AZs, but I think for those who have been using Kubernetes on the Google cloud it's certainly going to have a hard time competing with "you don't pay anything for HA masters at all."<p>> ingress<p>from the Twitch stream, it sounds like they have not worked out ingress with ALBs. No mention of Ingress on the announcement page. Twitch stream is here[1]. (it's over now) [2]<p>This is going to be super expensive to use in the near term.<p>Just now Nishi Davidson has just mentioned ingress/ALB is a focus of the sig-aws, so hopefully we can expect another announcement soon.<p>[1]: <a href="https://www.twitch.tv/aws" rel="nofollow">https://www.twitch.tv/aws</a><p>[2]: <a href="https://www.twitch.tv/videos/269722012" rel="nofollow">https://www.twitch.tv/videos/269722012</a>
AWS reacted to Google's (GCP's) success (Kubernetes), by trying to build a competitor, leveraging its market leadership position. A strategy which was very unlikely to succeed, from the get go.<p>Unfortunately for AWS, current market domination doesn't help much in this case. It cannot be solved by yet another two-pizzas team.<p>I believe that AWS is trying to fight (or downplay) the scenario in which, in a few years, when a lot of containerized workloads will be in production, GCP will be a force to deal with.<p>That's it. Plain and simple. My 0.02.<p>(disclaimer: I worked at AWS from 2008 to 2014 as tech evangelist, and I spearheaded the VMware+GCP partnership in 2015-2016 when I was vCloud Air's CTO at VMware - opinions here are my own, and are not based on any confidential information).<p>(second disclaimer: if you think the first disclaimer is not necessary here, you probably haven't worked much in large corporations, or at least didn't experience or witness the same things that I did).
I've been so excited for experimenting with EKS ever since the announcement but this offering looks very underwhelming.<p>With kops [0] I can spin up a production cluster on AWS quickly and have just as much functionality (if not more control) without paying Amazon ~$150/mo for the pleasure (per cluster!). It doesn't really seem to be "managed" either.<p>Maybe now's the time to really start to look at GCP/GKE. I've used them for some GitLab CI stuff in the past but never invested too much time into really seeing how the transition from AWS to GCP is.<p>[0]: <a href="https://github.com/kubernetes/kops" rel="nofollow">https://github.com/kubernetes/kops</a>
For those trying to spin it up while the docs aren't available, I ran into some issues with the IAM role.<p>Basically, create a new role with a trust relationship to `eks.amazonaws.com`, with the AmazonEKSClusterPolicy and AmazonEKSServicePolicy attached to it, and you should be good.<p>Thank you AWS, for having consistent naming schemes.
For interest: a CLI tool to simplify the initial process of cluster creation <a href="https://eksctl.io" rel="nofollow">https://eksctl.io</a>
any frontend eng from EKS, you should look at the chrome console.<p>"""
Warning: It looks like you're using a minified copy of the development build of React. When deploying React apps to production, make sure to use the production build which skips development warnings and is faster. See <a href="https://fb.me/react-minification" rel="nofollow">https://fb.me/react-minification</a> for more details.
"""
Are docs available yet? The pages aren't working for me.<p>- <a href="https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html" rel="nofollow">https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks...</a><p>Same with getting started guide - <a href="https://aws.amazon.com/getting-started/projects/deploy-kubernetes-app-amazon-eks/" rel="nofollow">https://aws.amazon.com/getting-started/projects/deploy-kuber...</a>
I am guessing it doesn't have Cloudformation support? So I have to spin up instances manually and this is 'generally available' for production use?