r/aws•
MadPhoenix

Timeline on EKS Preview?

Has anybody been allowed into the EKS (k8s-as-a-service) preview yet or have some information on a rough timeline? I signed up as soon as it was released at Re:Invent but haven't heard anything yet. Meanwhile, my organization is seriously considering a hybrid cloud architecture with Google or Azure in order to get onto a GA k8s-aas.

Posted Feb 26, 2018, 2:45 PM UTC

614
nathanpeck•

AWS employee here. We are adding small batches, but for popular previews like this one it can take some time to get in. Your best option is to talk to your AWS account manager or dedicated AWS solution architect support to put in another back channel request on your behalf.

5
Buremba•

hey there, could you please share info about the pricing? (since there are already beta users, i guess it's not confidential)

1
MadPhoenixOP•

Much appreciated!

1
menge101•

Talk to your AWS sales rep.

I've tried to get into previews before, and i've never been successful, but i'm small scale.

2
MadPhoenixOP•

Good tip, thanks.

1
meddlepal•

The lack of communication from AWS regarding EKS availability is... frustrating.

2
MadPhoenixOP•

Funny I was just thinking the same thing before I posted this, hmmm ... ;)

1
ut0mt8•

I am theorically in the first wave of beta testers. but still nothing here. On the other hand I ve just test kops and it is impressive. Perhaps we don't need Eks after all ?

2
MadPhoenixOP•

Kops is great but AFAIK it only covers deployment, what we are really looking for is a managed solution that also takes care of the entire lifecycle of k8s so we don't need to dedicate significant resources to training our ops team before we can get on the platform.

2
cuzzo23•

EKS is managed master nodes. Heres hoping, but I'm not sure if its going to be silverbullet as such.

I dont think its going to be at the scale which ECS is, but I've been wrong before.

1
jerutley•

Kops is impressive, but one thing I found as I deployed our first K8s cluster using it, it doesn't really take security of the cluster into account, at least not currently. The default is still AlwaysAllow instead of RBAC (which is an optional, but not default), it doesn't do anything to protect against Kubelet attacks originating from the containers it runs, and doesn't protect against trying to get stuff from the AWS metadata to compromise the cluster. Kops says it's there to deploy "production-grade" clusters on AWS, but until these issues are fixed, I just don't see it being there. And when you're a small shop like we are, trying to get started in this with minimal knowledge is a daunting task. I'd love EKS access just so we don't have to deal with these types of issues, and can let Amazon worry about it, but it's looking like that's not going to be anytime soon. Plus, EKS is going to be limited in which regions it can run in - your region MUST have 3 AZ's for EKS (or any kubernetes-based deployment) to be viable - without 3 AZ's, you're risking loss of quorum on your control plane, so zones like ca-central can't run EKS since it only has 2 AZ's.

1
goofygrin•

I'm in but my team has been too busy to dig in too deep.

Is there anything you're interested in?

2
Buremba•

what's the pricing?

1
MadPhoenixOP•

My basic eval would just be how it compares to Google and Microsoft's offerings in terms of architecture since I'm already familiar with those, but thanks for the offer!

1
[deleted]•

[deleted]

1