Kubernetes Reviews

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. 

At my company, we use Kubernetes to host our databases and applications. We work in the telecom domain, and our products use database technologies like Oracle, Postgres, and Cloudgres. We use Kubernetes to host NoSQL databases like Couchbase and Postgres and for some of our containerized applications. We are involved in multiple projects, not just a single one.

Kubernetes is a microservice. So, the best thing about Kubernetes is that most of the containerized applications are centralized. You don't need to develop specific company applications on top of container images. Kubernetes also provides flexibility in maintenance. It takes away most of the maintenance part, such as if a port crashes, it comes up automatically, making deployment very easy. We just need to run a few commands to deploy the application, and maintenance is taken care of by Kubernetes. Upgrading applications becomes smooth, requiring less effort and time.

Resource utilization, cost savings, and portability are additional advantages of Kubernetes. It is available in the public clouds, and portability becomes very easy. When it comes to networking, Kubernetes offers very flexible containerization with the added benefit of CSI.

There are several areas where Kubernetes could improve. For example, in one of our database projects, we needed a storage layer that would work on safer sites. Our application is a permanent one that requires low latency and is intensive in terms of networking. It works on every single URL and needs access to the database. After researching several solutions available in the market, we went with Portworx for the database back-end storage layer. However, we encountered an issue when we brought down one of the worker nodes in a cluster of three nodes. The pod that was hosted around that worker node was not responding on other worker nodes, even though it was responding. We found out that there was a feature in the alpha stages in the stable site that could have solved this issue, but we don't enable alpha features in our production environment. Therefore, we increased the replication factor in the storage layer from one to two to avoid this issue. Our application is latency-sensitive and demands low latency in terms of network and response time.

So, increasing a replica of the storage level will also cause double the I/O, which has additional costs involved. We did extensive research on that and found that the feature needs to be stabilized; certain improvements are required. 

I have been using Kubernetes for around two years now, and I'm familiar with it. I worked closely with both the implementation team and the engineering team as well as the research and development team.

It is a stable solution. 

Scaling up and down is easy in Kubernetes, so adding or removing worker nodes is simple and straightforward.

The engineering team uses it the most. We started with three projects, and now I can see around 150 to 200 people using it.

There is a good support community available.

It's free and open-source; anyone can use it. So there are no hidden fees or anything regarding Kubernetes.

I would encourage you to start with Docker containers first, get the hang of it, and then move on to Kubernetes.

Understand the Docker concepts, software, container networking, and how container images are built. Once that's done, it becomes easy to enter into the Kubernetes world. Kubernetes is an orchestration tool that builds on top of Docker containerization.

I would rate it as excellent because it is very easy to deploy applications, manage ports, and expose applications both within and outside the cluster. Kubernetes also has a good reach and can be used in both private and public clouds, and there is plenty of support in terms of documentation and online forums to help users who run into any issues. 

I was probably using Kubernetes from the operational side. The service requires high availability, ensuring 99.99% KPI for our customers. So, we primarily used Kubernetes for this purpose and for managing our services.

Kubernetes has everything. Its design structure is quite advanced, and its offerings are extensive. The practical feature was the seamless failover.

The big part has been the design of the environment and the configuration training itself. Then, they program in the test environment, establishing whether everything else is working. Once we hit the deployment on the test environment or the staging, we move to live. The challenging phase of that exercise is if you don't get the configuration right from the beginning to be able to adjust and change.

Kubernetes's configuration could be made easier, especially at the network level, including aspects like IPs and ports. Integrating it into our services was quite challenging.

I have been using Kubernetes for eight years.

The product is stable.

We service about three point four million transactions.

We had approximately twenty-two servers, with eleven on each side. So, we've got two sides, with eleven servers on one side being SQL servers. It took us about three months to set up the infrastructure, and the installation configuration took about one and a half months.

Six engineers were required for the solution's deployment.

The return on investment in terms of the services that we were offering was quite good. However, as we started to scale down, we lost the contract. Therefore, maintaining the environment then became very expensive.

The solution is expensive. The salaries of Kubernetes engineers were much higher. They came at a high price. Resources also came at a high price, and therefore, it became very expensive to continue with Kubernetes

The tool is not difficult to maintain, but if you've got problems, troubleshooting and devising can be challenging.

It was beneficial and very complex. The skills development for the team working on it was a little steep. It's more complex compared to other solutions similar to it. It's quite robust and nice, but the learning curve is steep.

In terms of resource management, for instance, if you run out of memory or usage capacity, Kubernetes seamlessly moves your workload from one node to another without any issues.

I recommend the tool primarily for enterprise businesses that can afford the cost associated with Kubernetes, including the end-to-end resources needed, such as people, systems, processes, and so forth.

Overall, I rate the solution an eight out of ten.

We use the solution to manage the containers efficiently.

The solution has a well-defined interface for every other function like network, CRA container, and run-time interfaces. It is fantastic as open-source software, very generic, and easy to use.

The solution's learning courses for the new users and developers must be easier to understand. Presently, they are very abstract, and it is challenging for users to find data.

I have been using the solution for a year and a half.

It is a stable solution.

The solution is easily scalable. I rate it ten out of ten. Our technical team for the solution consists of ten executives. At the same time, there are two million end users.

I took help from the solution's technical team for Stack Overflow. Their service was good, and I rate it ten out of ten.

Positive

We switched to Kubernetes for better scalability, maintenance, and administration.

The solution's initial setup was straightforward. I've used Rancher Kubernetes engine to set the cluster. The deployment took two days to complete. The process involved downloading the binary file and configuring it to servers.

We deployed the solution with the help of our in-house team. The team of three, including data engineers and data operations managers, execute maintenance for it.

I have seen a return on investment for the solution. 

We use the solution's open-source version.

It is easy to maintain distributed systems and applications using the solution. Although, it requires a few new features to improve managing the volumes. I rate it ten out of ten.

We use Kubernetes for deployment of TIBCO software analyst. We then use Rancher to deploy the Kubernetes cluster.

Kubernetes is POD technology so you can run the number of containers you need to host one by one and use similar microservices for the containers. This is a great feature of Kubernetes. The product provides auto rollback functionality and a scale-up and scale-down functionality. These are the main features that we didn't previously have. For scaling or restarting PODs or any services is very easy. We can configure the commands to easily scale up and scale down, based on the load requirement. If some business servers added more load, then we increase the POD, and increase the services. 

Kubernetes lacks some flexibility compared to other products such as OpenShift. 

I've been using this solution for four years. 

The solution is stable.

The initial setup is straightforward. We have our own Terraform script to deploy the Ansible. It provisions the orchestration and deploys Kubernetes and we install Rancher over Kubernetes and deploy the entire orchestration. We don't use any third parties. We carry out our own maintenance because we don't want to be dependent on third parties.

We use the open source solution and only move to the commercial platform for the purpose of node vulnerability. We use Instana and Qualys agents for security monitoring vulnerability purposes. 

For anyone wanting to use this solution, it's important to know the basics of Linux. In addition, Docker plays an important role and it's worth checking the YAML files before moving to Kubernetes. 

I rate this solution nine out of 10. 

I use the product for microservices. 

I am impressed with the product's coupling of resources and flexibility. 

The tool needs to improve its UI. The tool is very complex and basic. 

I have been using the solution for six months. 

We haven't encountered any issues with the product. 

I would rate the product's scalability an eight out of ten. 

The solution's setup is difficult and we need to write a lot of commands. It takes one day to complete the setup. We require two people for the solution's deployment and five people for its maintenance. 

I am using the solution's open-source version. 

I would rate the product a seven out of ten.