Kubernetes Reviews

Kubernetes is used t deploy all our applications. 

The deployment is one of the most valuable feature. The solution is also easy to use. 

The user-interface in regards to the other solution can be improved. 

I have been using Kubernetes since 2020. 

It is a highly scalable solution. There are twenty people using Kubernetes.

The initial setup and deployment is quite easy. We have one tech team and one Data Science team. 

If you are building an MVP or you are starting small, then Kubernetes might not be the best option because there are some charges associated with it.\  But if you are building an application that might scale rapidly, then you should definitely go with Kubernetes. 

If your deployments happen very frequently, then it is definitely the solution you should use, because you can restore previous versions if something fails.

I rate the overall solution a nine out of ten. 

The primary use case of the solution is container orchestration for a microservices-based architecture.

I worked on deployment in the cloud and on-premises.

The solution has improved our organization by providing a computing layer abstraction between the cloud provider and on-premise. This has given us higher consistency in management and deployment strategies. The solution also reduces the effect of discrepancies between development and production environments.

The most valuable feature of the platform is the auto-healing and auto-scaling ability to offload to the platform tasks that were previously managed by humans.

There is a large ecosystem of products surrounding Kubernetes, making it difficult to identify the right solution due to the vast number of options.

I have been using the solution for six years.

The solution is a stable mature platform.

Scaling is a straightforward and standard process. With the integration provided by the cloud provider, we can even enable automatic scalability.

Setting up without Kubernetes provider services is complex.

I give the solution a nine out of ten.

There is a large amount of overhead associated with maintenance, as we have to maintain everything from the operating system to the application. The cycle of updates and patches for the platform itself is very frequent, with a new version released every four months and various security patches in between. This makes the maintenance task very large if we have to do it ourselves.

The main benefit of Kubernetes is that it is currently the standard for container orchestration. Kubernetes is available across different cloud providers, providing consistency in management and portability that is not available with other products.

In the beginning, the solution may feel as if it has a lot of moving parts that are confusing and overwhelming.

Kubernetes is our platform of choice for running things in production, applications, and the like. Everything we build runs on Kubernetes, it's our platform of choice. I'm the principal devs engineer.

Kubernetes has improved our time to market because it's quite lightweight and easy to install. 

The most important feature is container orchestration. Kubernetes provides us with a mechanism to deploy or run in an automated fashion across nodes. I don't need to worry if it's running on node one or node two, it's all taken care of by Kubernetes. 

They have a very minimal interface to do certain things and that could be enhanced so that someone who is not as comfortable on CLI can also use the interface and play around with the cluster. Commercial offerings like Red Hat OpenShift offer it, but the open-source community edition from CNCF doesn't. I'd like to see an incubating project there. It's not one organization that is contributing to Kubernetes, it's a CNCF project, i.e. an open-source contributing forum.

They could possibly promote some data APIs to the production stage. They have a lot of APIs which are in beta stage which they continue to test. Perhaps it's time to upgrade them to a more product-release stage. I think it would offer peace of mind to customers in terms of stability. 

I've been using this solution for four years. 

This is a stable product if you are on a long-term support release. It's quite widely tested and used.

Kubernetes is highly scalable. We have around 150 users and it's used daily, mainly by developers and engineers. 

Kubernetes has a very active and vibrant community forum and people can join Slack Workspace and ask questions there. They announce new releases there too and people help out. If there are issues, you can open tickets, open GitHub issues and things like that.

We previously worked with Apache Hadoop but it was becoming somewhat cumbersome and complex to install.

Deployment complexity depends on the use case. I can install it on my laptop and it's easy but if it's being installed on production it needs to be set up in a cluster formation. That kind of deployment is moderately complex, and that's where we come into the picture, providing the automation for that. For someone without any knowledge in the area, deployment might require a third-party consultant or an integrator to help with that. 

I have some basic experience with Rancher and Red Hat OpenShift, which has a very nice graphical interface. An administrator, developer, or even a user can do a lot of stuff other than just seeing what applications are running. It's something that separates the commercial offerings from the community version of Kubernetes. If there were something like that in the open-source version, it would be a game changer. Of course, the commercial version also comes with hours of tech support and guides.

This solution is deployed on cloud with Azure.

Managing the container was a challenge. The cloud-managed Kubernetes allow us to take care of a big system and deployment and container management without having a big operational team.

It's still difficult to manage based on my experience. There are a lot of things that need to be done to get it up and running initially. It's very complex. The whole system required a big team, and that's why we were using the managed version. If we were not using the managed version, then it would have been very difficult to manage the system. Overall, it's very powerful, but there are also a lot of complexities to manage.

In the version that we're currently using, we still have to pull in a lot for different tools, like the distribution data, distribution tracing tool, etc. For it to be fully functional, we still have to deploy more tools into it. It should come with more default rules built into it for log aggregation, distributed tracing, and monitoring, so they can definitely improve upon those things. If they had better tool integration for monitoring and log aggregation, then it would be much better.

I've been using this solution for two years.

It's stable.

It's scalable. There are two different ways you can do it. You can manage it yourself, and then you're responsible for scalability software. But if you use a cloud solution, Google GKE and Azure have AKS and AWS had EKS. If we use those kinds of services, the scalability becomes easier to manage. It's definitely scalable, but even that part is very complex to manage unless you're using a cloud managed service.

It was very complex to set up the initial structure for Kubernetes. Using managed services made it simpler.

I would rate this solution 9 out of 10.

Kubernetes is used for cloud-native development. We deploy it to the hybrid cloud, like private in Azure and public cloud in Amazon AWS. Kubernetes is underlying, and we do not use Kubernetes directly. We use products that use underlying Kubernetes like OpenShift or Tanzu.

I like that it has really boosted cloud-native development and stood the test of time. The underlying architecture allows one to scale as per the business KPIs much faster. The underlying architecture is the master that works faster than the nodes. Then there are pods within those slave nodes, and there is a control pan as a part of the core architecture of the Kubernetes. Once you have the cluster up and running, you can monitor that and deploy your applications into the Kubernetes cluster. 

They should update Kubernetes more regularly. Kubernetes is open-source and supported by cloud-native communities. But there are other proprietary versions of Kubernetes like VMware, which runs Tanzu with underlying Kubernetes architecture, or Red Hat, which runs OpenShift. 

These have priority over the open-source project over the last five years. The Cloud Native Foundation is currently out with version number two. The first version came out 14 years ago. We really don't know when we will see another version or improvement with this totally open-source project.

Scalability can be improved. It should be flexible enough to run two instances that can be changed immediately to four, six, or eight swiftly. They could also simplify the logging process.

I have been using Kubernetes for about five years.

Kubernetes is stable.

Kubernetes is scalable because the underlying architecture allows you to scale faster.

The initial setup and installation are straightforward. You can install and deploy it within a matter of hours.

Kubernetes is open-source.

I would recommend it because of the microservices architecture that allows you to write cloud-native code in the Kubernetes environment. Kubernetes has become a leading choice for most big companies, and they are making their own products based on the underlying Kubernetes architecture. 

On a scale from one to ten, I would give Kubernetes a nine.

We use Kubernetes to orchestrate the containers for deploying our Docker images to Kubernetes. I'm an Azure DevOps lead.

Kubernetes has some advanced features like auto-scaling and a good self-healing facility. If Kubernetes runs in the form of ports and one of the ports dies, a new one automatically appears. These advanced features help us to deploy our application and makes life easier.

I find the auto-scaling feature very good because rather than manually decreasing the number of nodes, we can define the threshold.

The UI should be improved. It would be helpful if it was more graphical. Kubernetes currently runs perfectly with the Linux environment because it has Docker as a container runtime, and Docker works perfectly with the Linux operating system. It should also be able to run with the MacBook and Windows OS, similar to Linux and it would be helpful if they would include this in the next release. 

I've been using this solution for four years. 

The solution is stable. 

If you're using a cloud service provider there's no problem with scalability. When there's a newer version, we'll upgrade our Kubernetes cluster to the latest version. 

We previously had an on-prem solution using some tools like ClearCase, which is a centralized repository we used to work under. Given that everyone is migrating to cloud, we've done the same, migrating our applications to AWS and Azure Kubernetes.

Although it doesn't take long to deploy, Kubernetes is difficult to set up even if it's the small, mini one-node Kubernetes cluster. For a cloud deployment, it's either Azure or AWS. The cloud service provider will take care of the master node. We currently have a DevOps team of seven people. If we have a big cluster, we can it into multiple clusters, one for the Dev team, one for the QA team, and one for production; each team can work on its cluster and deployment can be done quickly. 

Pricing depends on the cloud service provider. Comparing AWS and Azure, Google Cloud has a much better pricing model, as does Linode. We receive a monthly licensing account.

It's important to learn the architecture of Kubernetes and know what each and every component of Kubernetes does. It makes the deployment easier. Whether or not you choose Kubernetes depends on your use case. If you have a business model that requires minimal changes with fixed requirements then Kubernetes might not be the way to go. If you're constantly needing to make changes, Kubernetes is a great solution. 

I rate the solution eight out of 10. 

This is a container orchestration platform used to organize our containers. Most of our applications are developed containers. We need Kubernetes to manage the network and volumes. We had approximately 50 tech team members using this solution. 

This solution is cost effective and fast. We are able to use Kubernetes to orchestrate hundreds of container images which has been a major benefit. 

There is a feature called Terraform and, based on the reviews I have read, it could be improved. 

I have been using this solution for two years. 

This is a stable solution. 

You can scale Kubernetes up and down easily.

When it comes to support, we have mostly used the documentation provided for the solution. 

The initial setup is straightforward but you do need to know the basics. The speed and ease of the set up depends on how fast you want the application to be and the amount of traffic your application generates.

When I first started using Kubernetes, it was quite challenging. I would rate the set up a two and a half out of five.

Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it.

We evaluated solutions like OpenShift and Rancher. The great thing about Openshift is that it is ready to use out of the box. When using Kubernetes, you have to set everything up on your own. Besides that, there are not many differences between Kubernetes and the other solutions. 

This is a very good registration platform. It saves costs and is fast. You can deploy thousands of replicas of your application all at once, as long as you have enough resources. 

I would rate this solution a nine out of ten. 

We use this solution for the hosting of micro-services. Kubernetes helps us to orchestrate all the containers hosting these micro-services.

One of the most valuable features is the ability to manage containers and pods. The solution monitors if applications are live and if issues are picked up, it automatically resolves these. This solution keeps our application in working condition. 

This is an open source solution, which gives the community the opportunity to request specific features which the Kubernetes team then work on and add to the solution.

We would to have additional features related to security within the API, instead of needing to install an add-on. 

I have used this solution for almost four years. 

This is a stable solution. 

This is a scalable solution. We are able to ramp up certain campaigns which this solution manages well. We have 400 to 500 people using this solution. 

This solution took one and a half years to get ready in production. We needed to explore a lot of add-ons in order to deploy into the Kubernetes cluster. 

This is a really useful solution that is particularly useful for organizations using micro-services. This solution is not suitable for use with monolithical applications. Kubernetes works well in an on premises or cloud environment.

The suitability of this solution may vary from company to company.

I would rate this solution an eight out of ten.