Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon EKS – Now Generally Available

aws.amazon.com

Post reply on HN
Print view View original

111–120 of 140 posts

Re: Amazon EKS – Now Generally Available

#111

Post by vira28 »

yebyen wrote: post #91
vira28 wrote: 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 announc…

Awesome Thanks.

Re: Amazon EKS – Now Generally Available

#112

Post by jpatokal »

foxylion wrote: post #52
nat wrote: post #29

Earlier quoted context omitted.

You're thinking like a human. There are plenty of organizations where $5/mo and $150/mo are essentially indistinguishable and would not affect decision making in any way.

I second this. This means you don't have to setup and manage those master nodes. AWS will do this for you. A developer fixing an issue with your self-managed master nodes will be much more expensive than 150$/month. As an individual this may look expensive, but as a company this is much cheaper than paying the loan of a developer.

I suspect you missed the point earlier: GKE offers a free managed master, even if your cluster is a single node costing you $5/month.

Disclaimer: I work at GCP, but not on GKE.

Re: Amazon EKS – Now Generally Available

#113

Post by derefr »

outworlder wrote: post #108
derefr wrote: post #41

Earlier quoted context omitted.

> "They're your nodes, you paid for them" seems like a reasonable position to take here. If that were a reasonable position, you'd think AWS RDS and Google Cloud SQL would give you superuser access to your database instances to do things like installing Postgres extensions. It seems a lot of people are happy to pay for instances they can't even SSH into. :/

I don't even want to SSH to instances that I control and have provisioned, why would I want to SSH into instances managed by AWS? Unless the point of your server is to provide SSH (you are using it as a development box, maybe?), having to SSH means that you are lacking in the tooling department. At work we are guilty of that. We are actively trying to improve on this.

In this case, it's not so much "SSH" as the ability to install files, as root, onto the server. For RDS/Cloud SQL, the inability to do that both restricts you from installing your own extensions; and restricts you from being able to use the Postgres COPY command with local/network-mounted (rather than network-streamed-to-STDIN) CSV files, majorly increasing the overhead of the operation and preventing parallelism.

Re: Amazon EKS – Now Generally Available

#114

Post by simonebrunozzi »

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.

Unfortunately for AWS, current market domination doesn't help much in this case. It cannot be solved by yet another two-pizzas team.

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.

That's it. Plain and simple. My 0.02.

(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).

(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).

Re: Amazon EKS – Now Generally Available

#115

Post by an_account_name »

simonebrunozzi wrote: post #114

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. Unfortunately for AWS, current market domination doesn't help much in this case. It cannot be solved by yet another two-pizzas team. I believe that AWS is trying to fight (or downplay) the scenario in which, in a few years, wh…

About your second disclaimer - are you worried someone would try to punish you for this comment, or are you trying to say that generally most commentators have undisclosed conflicts of interest?

(I work at Amazon but not AWS, opinions my own but geez I’m not gonna type that every time)

Re: Amazon EKS – Now Generally Available

#116

Post by yebyen »

an_account_name wrote: post #115
simonebrunozzi wrote: post #114

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. Unfortunately for AWS, current market domination doesn't help much in this case. It cannot be solved by yet another two-pizzas team. I believe that AWS is trying to fight (or downplay) the scenario in which, in a few years, wh…

About your second disclaimer - are you worried someone would try to punish you for this comment, or are you trying to say that generally most commentators have undisclosed conflicts of interest? (I work at Amazon but not AWS, opinions my own but geez I’m not gonna type that every time)

"You had an undisclosed agenda this whole time? How could you! I trusted you, anonymous stranger on the internet! This is an injustice that can never be forgiven!!!"

Get used to hearing this! Not the parent poster, but I've been on the receiving end of that.

Re: Amazon EKS – Now Generally Available

#117

Post by leg100 »

user5994461 wrote: post #106
sheeshkebab wrote: post #103

Earlier quoted context omitted.

Most environments (99.99%) don’t have thousands, hundreds, or frankly even dozens of machines to deploy to.

You're on hacker news, where technologists who run world class infrastructure congregate. The average number of servers per people who commented this news is over one thousand.

So they say. No one wants to back up a comment with "...and I run twelve machines". Could still be 'world class' tho.

Re: Amazon EKS – Now Generally Available

#119

Post by sho »

user5994461 wrote: post #106
sheeshkebab wrote: post #103

Earlier quoted context omitted.

Most environments (99.99%) don’t have thousands, hundreds, or frankly even dozens of machines to deploy to.

You're on hacker news, where technologists who run world class infrastructure congregate. The average number of servers per people who commented this news is over one thousand.

I seriously doubt that. 1000+ servers is a lot. The number of organisations worldwide running that many servers in any sort of coordination must be pretty low. Services (or "pods") sure, but actual servers? Can't be more than a few hundred companies, surely.

One would also think that by 1000-ish servers it's starting to make a lot of financial sense to move out of AWS anyway.

Re: Amazon EKS – Now Generally Available

#120

Post by markbnj »

darren0 wrote: post #80
ksajadi wrote: post #62

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. 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.

It's kind of a cynical position, actually, because embedded in it is the underlying contention that all of the attention the platform has gotten since 2015, the startups it has spawned, the resources being put into it by every major systems tech vendor, the doubling in size of kubecon every year for the last three years, the hundreds of how-to and in-depth articles that have been written, have all resulted from some sort of hype and anticipation of future benefits. There are thousands of nodes running production workloads right now. I've been running it in production since 2016. The value is certainly apparent to our team. Yes you can stitch a lot of it together with shell scripts and systemd or swarm or whatever. But why would you?
Post reply on HN