Amazon Elastic Kubernetes Service (EKS) vs. GoDaddy Container-as-a-Service (ElasticHosts, Springs.io), discontinued

It is well suited when you want to have a Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.

Incentivized

Unlike other providers, Springs doesn’t use a pre-built container solution, instead opting for their own software built from the ground up.

Incentivized

• Managed control plane
• Autoscaling

Incentivized

• Container hosting, cloud virtualization
• Elastic capacity scaling and pay-per-use billing
• Linux kernel containerization technologies for container isolation and control

Incentivized

• AWSIAM integration with Kubernetes RBAC could be better.
• Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
• EKS bootstrap time could be faster ...

Incentivized

• Provide more options at lower costs
• It would be nice to see that expanded out to more distributions. What would be potentially even better though is templates. Some hosts can deploy ready-to-run WordPress/Drupal sites, LAMP instances, ownCloud instances, etc. at the drop of a hat. If Springs could replicate this with their container hosting they’d immediately appeal to a much, much wider audience;

Incentivized

It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.

Incentivized

Springs is drastically cheaper than running 4 OVH servers, and a little cheaper than running nano instances on AWS.

Incentivized

• Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure.
• EKS Upgrade process to a new version seems to be taking very long ....
• EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes.

Incentivized

• In the beginning I wasn’t sure what I should set it to for my web server, so I left it. After a while the Average usage area begins showing how much resource the container is demanding and from that more adequate limits can be set.
• Springs is drastically cheaper than running 4 OVH servers, and a little cheaper than running nano instances on AWS.

Incentivized