Akamai Cloud Computing (formerly Linode) include scalable and accessible Linux cloud solutions and services. These products and services support developers and enterprises as they build, deploy, secure, and scale applications.
$5
per month
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.0 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
Akamai Cloud Computing
Google Kubernetes Engine
Kubernetes
Editions & Modules
No answers on this topic
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0000438
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Regular Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0000548
GKE Autopilot Ephemeral Storage Price GB-hr
Autopilot Mode - Spot Price
$0.0014767
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 3 year commitment price (USD)
$0
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0039380
GKE Autopilot Pod Memory Price GB-hr
Autopilot Mode - Regular Price
$0.0049225
GKE Autopilot Price GB-hr
Autopilot Mode - Spot Price
$0.0133
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 3 year commitment price (USD)
$0.02
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - 1 year commitment price (USD)
$0.0356000
GKE Autopilot vCPU Price vCPU-hr
Autopilot Mode - Regular Price
$0.0445
vCPU Price vCPU-hr
Standard Mode
$0.10
per hour
Cluster Management
$0.10
per cluster per hour
Cluster Management
$74.40 monthly credit
per month per hour
Standard Mode - Free Version
Free
per hour
No answers on this topic
Offerings
Pricing Offerings
Akamai Cloud Computing
Google Kubernetes Engine
Kubernetes
Free Trial
Yes
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
We have used Kubernetes as a single cluster. It works really well, and it is very good for dev, test, and preproduction environments. With minor DevOps it can be easily prepared for production. In short, it reduced time from development to production.
The thing that caught my eye was the price to start with. I move to Digital Ocean because they had better options for virtual network isolation, but I came back as soon as Linode fixed the issue. There support is great and things just work.
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.
Akamai Connected Cloud Linode would be a good service to host a content delivery network (CDN) because of its edge network but I'd prefer not to use Akamai Connected Cloud Linode for tasks that need GPU power such as Machine Learning or Artificial Intelligence (AI) because Akamai Connected Cloud Linode lacks deep GPU compute compared to AWS or Google Cloud or Microsoft Azure
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.
I've been with them a long time. They provide me with the capabilities I need coupled with knowledgeable support that's not pay-for-extra. However, if I move to a non-Linux OS, the level of support by necessity will drop off. I can still ask questions about the infrastructure but I my ability to ask about OS features will decrease.
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.
Simple and clear, no BS interface. From a design perspective it's no Apple or Stripe, but it does what it needs without making me want to stick a fork in my eyes, like when being forced to use Azure, AWS or GCP.
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
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
Servers are well dimensioned and price performant. Of course one always wants more, so if they were to upgrade their hardware for the same price I'd consider moving more workloads. Networking - never had an issue. Hardware speeds - disks are fast and can grow to great size.
Support was excellent and fast. The documentation is extensive and helpful. I learned many things from their online documentation. I did not contact them by phone, but email took a day or less. Complex problems would probably need a service contract. I liked the friendly and polite tone of the support.
Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
We switched to Linode from Namecheap due to poor uptime, and never had any issues with stability ever again after switching. We also cut our costs in half by switching. We compared Linode to DigitalOcean and Vultr, with the primary factor that caused us to go with Linode initially being their documentation. After using Linode for 3 years, their amazing support is another reason why we wouldn't consider anyone else at this point.
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.
Although I use only a fraction of their product offerings, the total set makes scalability an easy goal to shoot for. As I said, I have a few customers that use the services my Linode provides...and I like it that way. However, should I need to scale up, I can...without incurring any more cost than I need to.
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.