Live data from Hacker News

Amazon EKS – Now Generally Available

aws.amazon.com

91–100 of 140 posts

Re: Amazon EKS – Now Generally Available

#91
post #90

Noob here. I hear ECS, EKS, and Fargate. Can someone explain whats the difference between them and when to use one over another. Thanks.

ELI5: do you want to manage EC2 nodes and run containers on them? Use ECS (until you outgrow it. Why not... it is the cheapest of the three.)

Do you want to run Kubernetes in production, but afraid to do it yourself? (You probably know already who you are...) Container clusters composed of EC2 nodes, but joining the rest of the civilized world whose dev team thinks in the abstractions of K8S? Use EKS, today's announcement is for you.

Do you absolutely not want to manage EC2 nodes, but want to run containers? Use Fargate. Coming soon, Fargate for EKS will reunify the two threads.

Re: Amazon EKS – Now Generally Available

#92
post #80

Earlier quoted context omitted.

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.

>>> The value of containerizing your application is clear and has been realized over and over again. The jury is still out on k8s. The value of containerizing applications is negligible if there isn't the orchestration to go with it.

Not really, the value of containers that most people have seen is that it's just a more portable package. It's easier to move between environments in a consistent way. If I do that with fancy orchestration, shell scripts, or configuration management largely doesn't matter. I can get most of the advantages with shell scripts.

Re: Amazon EKS – Now Generally Available

#93
post #89

Earlier quoted context omitted.

What long tail do you mean? I would say the small tech companies with tens of developers and tens of servers are the long tail for AWS. The service is too expensive and too complicated to be used by very small companies or individual users. There are also more appropriate competitors in that space.

You told me you thought I'm not in the minority, and others have come forward to agree. I think we are the long tail. It is exactly as you say, companies that don't want to spend more than they absolutely need to on infrastructure. Shaving pennies to save money. We are each too small to make any significant money on us, taken individually. That's what makes us the long tail. Do you think in 6 months, you will be able…

Sorry, there might be a misunderstanding. I meant that you were not in the minority, in terms of user count. There are people trying out AWS/Google, riding on the free tier, or just running a small site for the experience. People spending less than a hundred dollars a month could very well be the majority of the user count.

It doesn't mean that they bring any significant revenues or that the distribution follows a long tail. I would actually bet that amateur users are not forming a long tail.

Re: Amazon EKS – Now Generally Available

#94
post #92

Earlier quoted context omitted.

>>> The value of containerizing your application is clear and has been realized over and over again. The jury is still out on k8s. The value of containerizing applications is negligible if there isn't the orchestration to go with it.

Not really, the value of containers that most people have seen is that it's just a more portable package. It's easier to move between environments in a consistent way. If I do that with fancy orchestration, shell scripts, or configuration management largely doesn't matter. I can get most of the advantages with shell scripts.

Deploying containers is shell-script-easy as long as nothing goes wrong. Ever. I know you know this. I'm a little confused why you'd make a claim like this.

Re: Amazon EKS – Now Generally Available

#95
post #86
post #80

Earlier quoted context omitted.

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.

Do you have any actual data related to this claim or am I just supposed to assume that it's true by inferring things from Amazon's cloud offerings? Edit: Sorry for the aggressive tone, I overreacted a bit because it seems like every single day there's someone pushing an anti-Kubernetes agenda on HN. Often they don't even use it, they just glanced at the docs and said "it's too complicated", or something. Clearly, thi…

I don't mean to push an anti-k8s agenda. What I'm pointing out is that people have conflated the value of containers with the value of orchestration and clustering. They don't need to go hand in hand. Containers without orchestration has been proven to save money. It's hard at the moment to prove the real value of k8s. It's too early and there isn't enough adoption. When you look at most success cases of k8s they often can achieve the same benefits using an plain old docker and some auto scaling groups.

Re: Amazon EKS – Now Generally Available

#96
post #27
post #17

Been 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…

In the launch video they asked about Ingress and it's apparently a work in progress.

AWS is taking over the ALB ingress controller that was developed for Ticketmaster with CoreOS. See SIG meeting nodes from the 1st: https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqyS...

Re: Amazon EKS – Now Generally Available

#97
post #92

Earlier quoted context omitted.

Not really, the value of containers that most people have seen is that it's just a more portable package. It's easier to move between environments in a consistent way. If I do that with fancy orchestration, shell scripts, or configuration management largely doesn't matter. I can get most of the advantages with shell scripts.

Deploying containers is shell-script-easy as long as nothing goes wrong. Ever. I know you know this. I'm a little confused why you'd make a claim like this.

It's really true for most users. I've seen it over and over again. Working in SV we lose sight of just how simple many peoples applications are. But I'm not saying just start a server and call it good. Use auto scaling groups, and some monitoring from your cloud provider. It's typically sufficient. Some of the most successful container deployments I've seen just use terraform + AWS services (EBS, ELB, ASGs). Its simple and gets the job done, not a lot of moving parts.

Re: Amazon EKS – Now Generally Available

#98
post #92

Earlier quoted context omitted.

>>> The value of containerizing your application is clear and has been realized over and over again. The jury is still out on k8s. The value of containerizing applications is negligible if there isn't the orchestration to go with it.

Not really, the value of containers that most people have seen is that it's just a more portable package. It's easier to move between environments in a consistent way. If I do that with fancy orchestration, shell scripts, or configuration management largely doesn't matter. I can get most of the advantages with shell scripts.

As someone who has worked in an environment where thousands of machines were being deployed to, this is ridiculous. Orchestration is an area where good tooling makes an absolutely massive difference. Shell scripts are not a good tool for observability or handling rollbacks.

Re: Amazon EKS – Now Generally Available

#99
post #37

Earlier quoted context omitted.

AFAIK, none of the big three cloud providers (GKE,AKS,EKS) lets you do this.

Yeah, none of the rest of the big three are asking you to pay anything for those masters at this point, though. "They're your nodes, you paid for them" seems like a reasonable position to take here.

Agree, really confused why AWS didn't follow Azure and GCP here.

(Disclaimer: I work for GCP, sorry for not making that clear in the parent comment)

Re: Amazon EKS – Now Generally Available

#100
post #97

Earlier quoted context omitted.

Deploying containers is shell-script-easy as long as nothing goes wrong. Ever. I know you know this. I'm a little confused why you'd make a claim like this.

It's really true for most users. I've seen it over and over again. Working in SV we lose sight of just how simple many peoples applications are. But I'm not saying just start a server and call it good. Use auto scaling groups, and some monitoring from your cloud provider. It's typically sufficient. Some of the most successful container deployments I've seen just use terraform + AWS services (EBS, ELB, ASGs). Its simp…

Auto scaling groups and ELB are world class orchestration. I can understand that you take it for granted if you already got that.

Containers are mostly useless without orchestration. A fancy zip file that can't distribute itself.

Outside of SV, the fight has never been to package applications, but to find some available servers where it can run and run it.

Post reply on HN