Akamai Connected Cloud (Linode) vs Google Kubernetes Engine comparison

"Because of the way that their pricing model is set up, I can scale up or down the size of a customer's server very easily. It makes life very easy for me when they run out of space, need more speed or RAM, etc. I can very easily pay the difference and reboot the machine, and now I have the upgrade that I wanted. That just makes it extremely simple."

"When it comes to the Linode Kubernetes Engine and the amount of automation it provides, it's awesome, it's a game-changer. If a process randomly dies, it could take me a while to notice that it has died, if I haven't set up monitoring. With Kubernetes, it will just restart itself using Heartbeats."

"The number one thing we like about Linode isn't necessarily a service, it's their support. We've found their support to be absolutely fantastic. They've been so outstanding with their support. Every single time we call them and we ask for advice or help, they go above and beyond and it's really made us appreciate what they do."

"The management of different DNS domains is beneficial due to the user-friendly interface that provides all necessary options."

"The solution integrates easily."

"Linode offers cost-effective pricing, and it enables me to swiftly deploy my services."

"For small businesses and people who have some technical skills and are good with Linux command line, this solution is great. I love Linode because it is very fast. Whereas, the same configuration on Azure and AWS will be so slow. The best thing is that their pricing and speed are great."

"The fact that you can get a person on the phone has just been fantastic."

"Its functionalities, such as computing the namespaces, clusters, pods, and restart logs, are easy to use."

"The main advantage of GKE is that it is a managed service. This means that Google is responsible for managing the master node in the Kubernetes cluster system. As a result, we can focus on deploying applications to the slaves, while Google handles any updates and security patches. The fact that GKE is fully integrated into the Google ecosystem, including solutions such as BigQuery and VertexAI. This makes it easier for us to integrate these tools into our process. This integration ultimately speeds up our time to market and reduces the time and effort spent on managing infrastructure. The managed aspect of GKE allows us to simply deploy and utilize it without having to worry about the technicalities of infrastructure management."

"The scalability is the best feature."

"I am satisfied with the stability offered by the solution."

"Google Kubernetes Engine (GKE) takes care of managing Kubernetes, including the main control plane. It also offers solutions for monitoring resources and handling external traffic, which is essential for us. Being a cloud-native solution, it relieves us from worrying about these operational aspects."

"The product has valuable security features. It can connect with multiple DevOps tools."

"We appreciate that it is quite easy to set up a Kubernetes cluster in Google Cloud, using the managed services within this solution."

"We hardly have a breakdown. It's been very stable."

"There is no notification from the company regarding upgrades."

"Right now, they don't have multiple data centers. They have limited data centers. I am currently using the Singapore and Mumbai data centers, but I am looking for data centers in Southeast Asia, the Middle East, and Africa. They need to improve the availability of their data centers and partnership engagements with cloud Panda solution providers, like us."

"I would like Linode (without cluttering things) to provide some type of DevOps workflow where people are configuring their pipelines from running their tests and deploying to their test server. Once approved by clicking a button, it just gets deployed to production. I would like something like Azure DevOps, which we use for large applications, and would be something nice to have in Linode."

"They don't have role-based access control, which is problematic for us."

"The only improvement in this aspect of the service which I can think of is perhaps a pool of developers who could be hired for those cases where the need goes beyond the support offered."

"It would be helpful if they provided the additional Linux distributions that I prefer using. But there is still a workaround. I can do it without direct support. It's a bit more complicated, but it can still be done."

"I would like to see more seamless integration with backup, although it's pretty easy to do."

"It would be nice if they had more data centers in Latin America."

"The management UI could be improved."

"While the GKE cluster is secure, application-level security is an essential aspect that needs to be addressed. The security provided by GKE includes the security of communication between nodes within the cluster and the basic features of Kubernetes security. However, these features may not be sufficient for the security needs of an enterprise. Additional security measures must be added to ensure adequate protection. It has become a common practice to deploy security tools within a Kubernetes cluster. It would be ideal if these tools were included as part of the package, as this is a standard requirement in the industry. Thus, application-level security should be integrated into GKE for improved security measures."

"The pricing could be more competitive. It should be cheaper."

"Google Kubernetes Engine is less stable in some highly complex deployments with many nodes."

"The console for this solution could be improved because it is very limited."

"The user interface is a bit confusing sometimes. You need to navigate between the various consoles we have. It's hard to figure out where things are. It's frustrating. The documentation could be a bit better."

"It needs to support load balancing."

"There is a limitation for our infrastructure. It's very complex to see in one dashboard all the components and all the behavior on performance. I am looking for some additional tools for that. If I want to check the disk or file storage, it gets complex. There should be an integrated dashboard so that we can manage everything through a single pane."

"I pay $5 per month for each of three servers, for a total of $15 per month, and I normally prepay a few months in advance."

"It is quite affordable, which makes it a great choice."

"The pricing model is simple."

"Currently, we are at $40 a month but they have costly solutions as well."

"The pricing model is very simple. I like the simplicity of it, starting at $5, then doubling as it goes up from there. That is a brilliant idea, and it is not complex at all. It is about as dead simple as you can imagine. So, if you want to double what you have, then you double your price, pay the money, and reboot. It is done. It's that simple. You can't beat that."

"When we started with the service, the cost was approximately €5 per month."

"The monthly cost depends on your requirements."

"There might be something a little bit cheaper but I find it very fair and competitive, and nothing to complain about."

"The product is a little bit expensive."

"I would rate the solution's pricing a nine out of ten. The tool costs around 3000 dollars per month. There are no additional costs apart from these."

"Pricing is a bit expensive compared to some other products, but it's acceptable."

"The price for Google Kubernetes Engine could be lower - I'd rate its pricing at three out of five."

"We are planning to use external support, and hire a commercial partner for it."

"I would rate Kubernetes' pricing four out of five."

"Currently, it costs around $1000 per month which sorted our deployment. So once we get more clients, having a huge suffix, costs can go up."

"The pricing for GKE is dependent on the type of machine or virtual machine (VM) that is selected for the nodes in the cluster. There is a degree of flexibility in choosing the specifications of the machine, such as the number of CPUs, GPUs, and so on. Google provides a variety of options, allowing the user to create the desired cluster composition. However, the cost can be quite steep when it comes to regional clusters, which are necessary for high availability and failover. This redundancy is crucial for businesses and is required to handle an increase in requests in case of any issues in one region, such as jumping to a different region in case of a failure in the Toronto region. While it may be tempting to choose the cheapest type of machines, this may result in a limited capacity and user numbers, requiring over-provisioning to handle additional requests, such as those for a web application."