Kubernetes Reviews

We are basically integrators for Kubernetes because it is open source. And if we go further for any supported version, like Red Hat OpenShift or AWS EKS, Azure AKS. So Azure Kubernetes Service and Elastic Kubernetes Service. So that's where we are a partner as well, partner and integrator.

Our clients use it mainly for application modularization or new applications in microservices, build, and deployment. So where, like, if the client was running it on a monolithic application or legacy application, and they wanted to refactor their application, we convert it to microservices. That means building those container images, and then running them on a platform like Kubernetes so that it can run across different nodes across the data center, and we can manage it. 

Basically, it is more of running as container images. So whenever that application requires more scale-out, features, refactoring, or application modernization, that's where we use this Kubernetes platform to run such applications.

There are many good features. I feel that the scale-out features, like replica sets, are very good. The number of running containers can be autoscaled. So, if there is more load on the application, it will automatically replicate the number of container images running. I feel that that is a very good feature, where there is no need to worry about the incoming load or response time or taking care of scaling. It automatically takes care of it.

Kubernetes is open source, which is both beneficial and negative depending on the responsibilities. Supported versions like Red Hat, Amazon, Microsoft, or Google are pricey. 

It's good for bigger organizations, but for smaller organizations or a few workloads, it may be too heavy, not easy to deploy, and the ROI may be less because it requires a control plane, worker nodes, and multiple VMs to run. It's good for bigger organizations where many applications are run, but overkill for handling one or two small applications.

I've been using it for at least the last four or five years. I've been solutioning and setting it up on various cloud providers like AWS and Azure.

It is quite stable compared to three or four years ago. If you are using a supported version and not a very old version, then it is good.

It is scalable. We can add nodes and then more container images.

Some plugins for monitoring, patching, and operating are automatically available, so those are easy. Some may not be, like in the case of an older environment that may not have supported plugins, so those have to be developed.

The customer service and support are satisfactory. Setting up is more effort-based. Later on, it is okay. Lab features and admissions are required.

Positive

It requires initial effort. Later on, managing is okay, but initially, it requires skilled people to deploy it properly due to networking between nodes and worker and control planes.

The deployment time varies depending on the deployment. A simple POC for one VM can be deployed in an hour. For a dev-test environment, it may be around two hours. For production with many nodes, it may be four to five hours. It depends on the configuration, deployment type, and number of nodes.

Kubernetes improved the deployment and scaling processes. It requires underlying infrastructure nodes, which are a control plane (sometimes called a master plane), and worker nodes to run images or workloads. Because the underlying servers or virtual machines can be autoscaled or provisioned through policy, there is no need to take care of the rest. Once the application is deployed as a container image, Kubernetes automatically scales. It's just a matter of adding servers as worker nodes on which multiple applications or microservices can run. There is no need to deploy again.

In a typical scenario, we used to create virtual machines, install operating systems like Windows or Linux, and then deploy the application. Kubernetes eases deployment time, and we can run multiple applications from containers on the same node. 

Even for each application, there may be different types of containers, like for front end or middleware connecting to a database. So there are a couple of such options.

For deployment, around one person is good enough for an average setup. For support, one to two people are required, at least one person for each shift.

I would rate the pricing a six out of ten, with ten being expensive. It's a bit costlier for smaller organizations.

It's good for bigger organizations, but for smaller organizations or a few workloads, it may be too heavy, not easy to deploy, and the ROI may be less because it requires a control plane, worker nodes, and multiple VMs to run. 

It's good for bigger organizations where many applications are run, but overkill for handling one or two small applications.

I would recommend using it. 

I would rate it an eight out of ten, with one being bad and ten being very good. 

We produce software that connects multiple Kubernetes clusters together. All 50 employees of our company use Kubernetes.

We're building an application for Kubernetes users to consume.

We're creating CRDs for our software, so I would say maybe that the deployment model of Kubernetes is simpler than the life cycle management.

The network policies and RBAC management across multi-clusters could be improved. This is an issue we're trying to solve in the market.

I've been using Kubernetes for around four years.

I rate Kubernetes eight out of 10 for stability. 

For a single cluster, I would rate Kubernetes eight out of 10 for scalability. 

Deploying Kubernetes is complex. If you are deploying Kubernetes as a standalone solution, it's complex all around. However, it's a bit easier if you use one of the cloud providers' managed services.

We deploy it on the cloud. I have the deployment scripted, so it only takes me 10 minutes. I wrote Terraform scripts for that. We have about six people on our DevOps team. 

If you're switching from VMs to Kubernetes, you will see a return because you can pack more into the Kubernetes architecture using containers rather than VMs. You'll see some more savings on your infrastructure, as well.

The cost depends on the cloud provider, so I would give it a six out of 10 for affordability.

I rate Kubernetes a solid eight out of 10. It's only going to grow as time goes on. I recommend contacting a professional to help you deploy Kubernetes.

We use this solution to containerize applications. Some of these applications function in Jira, the local tool center. There, we push them to a centralized platform.

It has a complete loading feature set for replica site deployment.

Currently, in Kubernetes, all of the health deployments or monitoring, and the discrete tools need to be configured. Changing this would make it much easier. Otherwise, we have to rely on a external tool to implement the monitoring.

I have been using Kubernetes for a year and a half 

The stability of the solution is a nine out of ten.

The scalability is good. Ten users use this solution at present. 

The initial setup takes twenty minutes. 

Overall, I rate the solution a nine out of ten.

We use Kubernetes to deploy a software solution that the company sells to enterprises. Originally, our company offered their software installed without Kubernetes, but they plan to move all future customers to Kubernetes. I would say it's extensively deployed, and they plan to increase it as much as their customer base will accept it.

Kubernetes provides a standardized way to deliver software in a scalable form. The customers of the software already have people who know how to manage Kubernetes, or they can easily hire employees who do. Packaging up the software to run would require a lot of specialized knowledge.

Kubernetes provides scalable clustering for containers and other means of deployment.

Kubernetes is incredibly complicated, so one area of improvement is the ease of administration. I would like a user interface that you can run to help you debug and diagnose problems and suggest how to configure things.

I've been using Kubernetes for about four months. I started using it at HPE and actually switched to be able to work more with it at the new place.

Kubernetes is generally stable. 

Kubernetes is scalable if it's well-administered. 

As far as I know, there's not any customer support. There's customer support for the cloud instances. If you are running Amazon EKS, they might have support for that. It's open-source software, so there isn't Kubernetes support, but I could be completely wrong about that.

The complexity depends on how you deploy it and what flavor you choose. If you're using a cloud provider like Google, AWS, or Azure, they each have a flavor of Kubernetes you can deploy. It is easier to deploy one of those than downloading and installing it on your servers. There's also something called K3S, a lightweight version of Kubernetes that can run much more easily. It's designed to be used in the Internet of Things. It's relatively scalable and can be used independently, but there are different packages, just like Linux has different distributions.

The maintenance required also depends on how you implement it. It's going to require at least one person who knows Kubernetes. I imagine it might need multiple people to maintain the solution if you're not using the cloud versions.

Kubernetes is open source.

I rate Kubernetes 8.5 out of 10. My advice is to hire people who have demonstrated experience or are prepared to spend significant time taking courses because it's deep and broad, and there's a lot to learn. It isn't straightforward, but it would be hard to simplify it, considering what it does.

At our company, we use the solution internally and integrate it with other products. Kubernetes is helping our organization shift from bare metal servers to cloud infrastructure. 

At our company, we use the solution to create nodes and multiple databases for our organization's clients. Kubernetes also helps me run SQL servers and other similar applications. Using some internal tools at our company, we convert our Kubernetes virtual machine into a GUI-based system that works seamlessly. 

The solution also helps our company develop custom hosting solutions across different servers. The cost of developing custom solutions is also reduced by utilizing Kubernetes. 

Kubernetes helps seamlessly build cloud infrastructure for development and testing. The tool assists in the production of small-scale databases for SMEs. Kubernetes empowers the customization of products developed by our company and accelerates the development process. 

With Kubernetes, a complete product with major functionalities can be developed in a day or two, as might have been discussed by a company in the SOP. MVP or demo product development is also possible with Kubernetes. The development of applications with all required components by the client, including the infrastructure, backup, security, and operating system, becomes very fast with Kubernetes. 

The most valuable features of Kubernetes for me will be automated rollouts or rollbacks, storage orchestration and high-end availability. The storage tasks and load balancing of applications also become easier with Kubernetes.  

The virtual machines from Kubernetes should be GUI-based. The virtual machines can be used only as a command prompt or CLI with Kubernetes. It should allow integration with other interfaces developed using different open-source technologies. Kubernetes should provide centralized free training that is easily available. The product should be made more viable and user-friendly for innovative users. 

I have been using Kubernetes for two years. 

The solution is stable, but there are glitches occasionally. At our company, we are using Kubernetes for customization, so glitches are expected. 

The solution is scalable, but it's mostly based on bare metal servers, so a user cannot exceed a specified limit. Suppose I have a fifteen-core CPU; then, all the nodes will simultaneously use all the resources, which can lead to downtime in the server. When you try to work with proprietary or open-source systems like Kubernetes a common error occurs where the database backup is not utilized. 

The solution provider's customer support needs to be improved. I would rate the customer support as six out of ten. 

Neutral

The product's deployment is straightforward. Only experienced and trained engineers can carry out the deployment. The solution's deployment can be completed within a couple of hours, even if it includes scripting or creating a development/testing environment. But in some rare cases the deployment time can be longer if it involves extensive R&D. 

About three professionals are needed for the deployment of the solution: one architect, one developer, and another individual for maintenance. 

The solution can generate a good ROI and save 50% of the cost for a company. 

It's an affordable solution. I would rate the pricing a five out of ten. 

At our company, we have worked with KubeVirt as well. KubeVirt helps our company convert CLI to a GUI-based product. 

I would rate Kubernetes as seven out of ten. I would advise others to learn Python or YAML programming language before using Kubernetes. 

We have multiple use cases. We use it for pharmacy applications, databases, MySQL and web servers. We use Kubernetes for anything that runs normally.

The high availability of containerization is most valuable. We get density with planning containers, and the self-serving feature allows our developers to grab a container and complete testing. The self-serving feature is always in the cloud or locally integrated with Ceph or cluster.

The front end of Kubernetes could be built better as the front end is very rudimentary.

We have been using this solution for about five years. It is deployed both on-premises and on cloud but mainly on-premises.

It is a stable solution, and we don't have any issues.

It is very scalable. We can scale up, add notes, scale out horizontally, and scale the number of containers in a web server. We add triggers to the cluster, and it scales as needed. We have quite a few users of Kubernetes at our company, and it is very easy to add new developers as users.

The initial setup was straightforward. For testing, we fire up Kubernetes clusters about once a week for different departments. Depending on the containers, it generally takes about four hours to get a cluster up and running and connected to the storage. We've completed this many times and are familiar with the setup. We completed the setup ourselves.

The Kubernetes community edition is free, but we use OpenShift in production, which is the Red Hat version of Kubernetes.

We evaluated Swarm and some other solutions, but we eventually chose Kubernetes and OpenShift.

I rate this solution a nine out of ten. Regarding advice, in the retail field, where clients would require mobility and portability, and disposable computing, there is no comparison to Kubernetes.

We use the product to manage application deployment by troubleshooting and collecting logs.

The most valuable features of Kubernetes have been autoscaling and its resilience mechanisms.

The platform could be more convenient to use. While the Kubernetes CLI is powerful, the interface needs to be improved. The users often navigate between various third-party IDEs. Thus, a more consolidated or standardized interface could streamline the user experience, allowing easier access without the need to balance between multiple tools.

We have been using Kubernetes for three years.

The platform is stable. However, it depends on the cloud configuration. I rate the stability a ten out of ten.

The product is scalable. We have 20 Kubernetes users working on and deploying it. We plan to increase the usage.

We contact Microsoft in case of any queries as we are working with Azure Kubernetes services.

The complexity of the initial setup depends on Kubernetes services. It is easy to configure while working in an Azure environment. The Azure portal simplifies the process through configurations with tools like Terraform. It is complicated to create the platform on virtual machines and on-premise machines. We can deploy it within 20 to 30 minutes using data pipelines.

Microsoft provides reasonable costs for Kubernetes.

I advise others to work with Kubernetes if they are developing or running the cloud native configuration. However, there are more cost-effective solutions. I rate it a nine out of ten.

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.