DEV Community

Cover image for DigitalOcean Kubernetes VS AWS EKS from My Perspective when Used Both of Them
andre aliaman
andre aliaman

Posted on • Updated on

DigitalOcean Kubernetes VS AWS EKS from My Perspective when Used Both of Them

Digital Ocean and AWS show their support for Kubernetes with creating special product for Kubernetes which we can use directly for each cloud. Each of them has their advantages and disadvantages. With this article, I would like to share my experiences during use each of the services.
Here are a few summaries I can conclude using both of the services:

Creating the cluster

Digitalocean support creating Kubernetes cluster directly with their control panel and CLI, Although you can't find official support for creating cluster with CLI(only in community question). Find the docs how to do it at
Digital Ocean Docs with control panel and Digital Ocean Docs with CLI

For Kubernetes Cluster with AWS, you need to create the cluster on top of the VPC. If you don't specify the VPC, it will create the new one. If you want to create the cluster on top of exiting VPC, you can follow my guide at here

Support Kubernetes Version

For Kubernetes version, Looks like Digital Ocean always support the last three version from Kubernetes. You can see at below (when this article publish)
Alt Text

For AWS side, it's a little bit different. AWS doesn't support a latest Kubernetes version that fasts. When publishing this article, this is what AWS support for Kubernetes version right now:
Alt Text
Check full documentation at here

Ingress support

Digital Ocean supports all popular ingress controllers like the Nginx, Contour, HAProxy, and Traefik. You just need to choose one of them.

AWS itself has their ingress controller, which support and used their ALB services. Here the docs
and How to use it in real case, you can follow this guide

Another ingress controller which support by AWS is Nginx controller for NLB. this is the docs

Support by third party (marketplace)

Digital Ocean has a marketplace that supports their Kubernetes services directly. You can check below or open here
Alt Text

For AWS, You can check this docs which they announce, some of paid container supported at EKS

Cost

For Cost, Digital Ocean gives a free for the cluster. We only need to pay for worker nodes we used. Check at images below:
Alt Text
or check here

AWS just announce they cut a cost for deploy the cluster (yes, we still need to pay for their cluster services and for each worker node we used).

Alt Text
Full news check at here

AWS also apply some restriction for total pods which we can deploy and have access to the interfaces. Check here. So we need to be extra cautious when we plan our cluster.

Conclusion

From the several comparisons above, we can conclude, Every platform have their advantages and disadvantages. Looks like AWS will be more good if we use their Kubernetes product with their supporting application like ALB, VPC, etc. If not, Maybe we can consider using Kubernetes services from Digital Ocean since their Kubernetes services support almost all the open source like ingress directly. Try to match with your needs is the key. Have fun when doing the explore.

I think that's it for this article discussion. Leave a comment at below about your thoughts! Thanks.

Top comments (0)