DigitalOcean's Managed Kubernetes is designed for simple and cost effective container orchestration.
N/A
Google Kubernetes Engine
Score 8.0 out of 10
N/A
Google Kubernetes Engine supplies containerized application management powered by Kubernetes which includes Google Cloud services including load balancing, automatic scaling and upgrade, and other Google Cloud services.
$0.04
vCPU-hr Autopilot Mode
Kubernetes
Score 9.1 out of 10
N/A
Kubernetes is an open-source container cluster manager.
DigitalOcean is the most affordable and straightforward of the hosted Kubernetes options we evaluated. All features that we require are supported without an excess of complication of extraneous features. Straightforward billing is also very important for us in comparison to the …
Our organization went with Google's Kubernetes Engine because we are already significantly invested in the Google Cloud Platform. In our evaluation of Amazon's Elastic Kubernetes Service we were turned off by recent concerns about Amazon becoming overly dominant in the cloud …
GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.
We had to move several products to Google Cloud, and the Google Kubernetes Engine was the option recommended to us, so we investigated it and ran with it. Back then (2019), we were not aware of Cloud Run-provisioned K8s clusters, so our other option was a completely …
In comparison to functionality with EKS and AKS, it has a better upgrade path and the price is lower. Not sure why flannel is the primary overlay network provider but network policies are supported as well.
DO Kubernetes is well-suited for: - deploying APIs - deploying workers - log collection and analysis (ie ELK stack) - deploying Helm charts and anything that can be mapped on to K8s concepts Less appropriate for anything requiring no public Internet access (ie VPC only). Less appropriate for anything requiring integration with the DO app platform via VPC, at the moment.
If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Engine upgrade rollout strategy - well documented and configurable
Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.
DigitalOcean is the most affordable and straightforward of the hosted Kubernetes options we evaluated. All features that we require are supported without an excess of complication of extraneous features. Straightforward billing is also very important for us in comparison to the Big Three cloud hosts, which have very complicated billing practices. DigitalOcean also provides a platform with very little vendor lock-in.
GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.
