For interest: a CLI tool to simplify the initial process of cluster creation https://eksctl.io
Amazon EKS – Now Generally Available
71–80 of 140 posts
Re: Amazon EKS – Now Generally Available
#72Been waiting for this for... 7 months now since its announcement at ReInvent? My initial impressions are very negative. What even is the point 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, b…
EKS may be appealing for a shop that has AWS expertise, automation, and monitoring set-up already and that doesn't necessarily want to manage a completely different stack for k8s. EKS has some form of integration with IAM, EBS, ALB, Route53, CloudWatch, etc.
As to 'unfinished', this is the usual model for AWS. New services are initially very simple and rich features and integrations are added over time. It's been that way for ten years. ECS didn't even support running multiple container ports per instances when it was released!
Re: Amazon EKS – Now Generally Available
#73Earlier quoted context omitted.
Do you think management nodes are free? Master nodes need to run etcd+kube api. These master nodes are multi region available with HA configured, which will be expensive even if you use smaller instances yourself. Google might be free but if you are already in AWS and do not want to manage Kubernetes masters at all and treat your worker nodes like cattle, it is a very nice and enough solution. What integration do you…
> Do you think management nodes are free? ... Google['s management nodes] might be free Indeed they are. Why do you think that is? It could be that they're a great big loss-leader for GKE, or that the costs of GKE management nodes are amortized into the per-cluster-node costs. But neither of these seem to be true. (The pricing of GKE management nodes before they made them free was negligible; and GKE nodes don't cost…
It’s subsidized by AdSense. Like every Google product.
Re: Amazon EKS – Now Generally Available
#74Earlier quoted context omitted.
HA seems like a poor choice as a default. I don't want to pay ~$150/month for dev and staging clusters, and I certainly don't need them to be HA. IIUC, Google/GKE and Microsoft/AKS are single-zone by default... free for masters, but not free for HA.
Until recently gke was charging 0.15/ hour too, so aws is just a little behind https://cloudplatform.googleblog.com/2017/11/Cutting-Cluster...
Not only recently, but actually this was the cost until yesterday for GKE with HA masters distributed across AZs[1]!
I only heard that this announcement from AWS was likely coming this morning, over here in the thread about upgrading GKE clusters[2]. Given how long we've waited since the announcement at November's re:Invent, there's honestly not a lot that seems terribly rushed about this news, but I bet that AWS really would have liked to have Ingress controllers that are integrated with ALB ready for this announcement to go with their CNI plugins.
"Why am I waiting for Amazon to get out of preview when Google's been giving it away this whole time?" For AWS customers that aren't locked in, that seems like a reasonable train of thought.
[1]: https://cloudplatform.googleblog.com/2018/06/Regional-cluste...
Re: Amazon EKS – Now Generally Available
#75Earlier quoted context omitted.
And they will all die pretty quickly for running their infrastructure on a pre emptible instance to save a few dollars. By the way, startups get $100k free credits on each of the major clouds.
You can afford ~5 preemptible instances for the cost of one full-time instance. I think you are severely overestimating the harm that is done by preempting/terminating instances in a prod Kubernetes cluster that is capably configured for full HA and distributed across zones. That's what it's made for – nodes are as disposable as pods. They may come and go as they please, and they'll be replaced as needed by the self-…
Your message obviously implies that you have no experience with what you are suggesting, hence why you don't realize the downsides.
Re: Amazon EKS – Now Generally Available
#76Earlier quoted context omitted.
You can afford ~5 preemptible instances for the cost of one full-time instance. I think you are severely overestimating the harm that is done by preempting/terminating instances in a prod Kubernetes cluster that is capably configured for full HA and distributed across zones. That's what it's made for – nodes are as disposable as pods. They may come and go as they please, and they'll be replaced as needed by the self-…
Your message obviously implies that you have no experience with what you are suggesting, hence why you don't realize the downsides.
"No experience" is a stretch. I'll concede, no significant Prod experience to speak of.
I got introduced to the Kubernetes ecosystem when Deis Workflow was rebuilt for it. Today, I'm a core contributor on the team that is building the fork of that project.
(It is a side thing for me. I'm very interested but I'm not spending hundreds on infrastructure every month. I have an infrastructure team at $dayJob, and they are not doing K8S at all, if you are having a hard time understanding how exactly I got here.)
Re: Amazon EKS – Now Generally Available
#77Earlier quoted context omitted.
Google and Amazon are enterprise services. If you consider $150 too expensive, you are not part of the target customers.
The Google GKE offering can operate with a single g1-small worker. That's $0.0257/hr or $0.0070/hr preemptible. $5/mo minimum* This is not even the same ballpark. *(to be fair, the $5/mo minimum does not include a private network and a load balancer, and you will almost definitely need both in order to actually do anything with a cluster.)
You can set up the nginx controller with NodePorts to get rid of the load balancer if it's just a side-project cluster. (Otherwise load balancers will be the majority of your cost)
Re: Amazon EKS – Now Generally Available
#78Earlier quoted context omitted.
That's $150/mo before you even launch a single worker tho. I don't know about you, but I'd personally rather pay the $5 if I don't need a serious cluster yet. How much in actual absolute dollars do you think this is going to cost you, just in order to figure out exactly how it works, and what other AWS widgets you'll also need to pay for in order to use it effectively? I am a human, basically looking for a stepping s…
I'm pretty clearly in the minority with my opinion here, and I recognize that. Amazon has made a substantial investment in Kubernetes here and that is nothing to shrug at. They are entitled (and justified) to recoup it. It's fair to say that K8S is not for lightweights, too. AWS provides a fairly generous free tier and they are also justified to extract some payment from every user of their services that derives some…
You're not in the minority. It's well understood that there are amateurs trying to use the expensive clouds and shave off every penny, while the main customers are enterprise customers who couldn't notice a thousand dollars more or less.
It's just pointless for small users to argue about AWS costs. The service is not meant for them and it cannot fulfill their requirements.
Re: Amazon EKS – Now Generally Available
#79Earlier quoted context omitted.
I'm pretty clearly in the minority with my opinion here, and I recognize that. Amazon has made a substantial investment in Kubernetes here and that is nothing to shrug at. They are entitled (and justified) to recoup it. It's fair to say that K8S is not for lightweights, too. AWS provides a fairly generous free tier and they are also justified to extract some payment from every user of their services that derives some…
You're not in the minority. It's well understood that there are amateurs trying to use the expensive clouds and shave off every penny, while the main customers are enterprise customers who couldn't notice a thousand dollars more or less. It's just pointless for small users to argue about AWS costs. The service is not meant for them and it cannot fulfill their requirements.
You're obviously no slouch, and I respect your opinion, but I think Amazon is all about the long tail and without speculating too much about what they are thinking, I'll say they might disagree. They are obviously smart to go for the big money dollars first, but everything I know about "Long Tail" says you're wrong.
I absolutely agree with everything you said, if you only added "at this time" to the end of that last sentence.
Re: Amazon EKS – Now Generally Available
#80I 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. 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…
Amazon is extremely data driven. If their attitude is lukewarm at best then you might consider the market is lukewarm at best.
People take for granted that the value of k8s has been proven. It has not. The value of containerizing your application is clear and has been realized over and over again. The jury is still out on k8s.