Kubernetes Reviews

The most valuable features of Kubernetes are the integration with Docker and there is plenty of documentation available. We work with Docker as a container, and it is more integrated with Docker than VMware Tanzu.

Kubernetes could improve by having better integration with VMware solutions.

I have been using Kubernetes for approximately three years.

Kubernetes is stable. They are the leader in their category.

If the platform for Kubernetes is VMware it is not scalable, but if the platform is Linux, it's scalable.

There are approximately 15 developers and five network administrators using the solution in my organization.

The technical support from Kubernetes is good.

I have used VMware Tanzu previously and I would like to work with it more because it is better integrated with other VMware solutions, such as vCenter, vSphere, vSAN, and NSX.

I have done the initial setup of Kubernetes many times, for me the setup is easy. If I am focused I can complete the full implementation in one or two days.

We have received a return on investment from using Kubernetes.

The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually.

Kubernetes is the leader in this category, and are very good. However, if the platform they want to implement is VMware, I would advise using VMware 10.

I rate Kubernetes 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. 

This solution is used for serving DevOps.

Kubernetes is quite controversial. It increases developers' overhead and allows them to provide trolling updates and zero downtime. In addition, it has increased the possibility of delivery of new features without training downtime of the application.

All the current features are quite harmonic, and they require each other.

We have been using this solution for about two years, and it is deployed on the public cloud.

I rate the scalability a ten out of ten. It is infinitely scalable, and no feature can scale like Kubernetes. How much we use the solution depends on the company's business needs.

We did not use other solutions and have only used Kubernetes.

I rate the initial setup a four out of ten. It requires call writing come, YAML files and help to chart things done. You need to add something new to improve the solution and handle the traffic. The deployment was completed in-house, and one person was enough to complete the deployment.

We have not seen a return on investments. It's saved the possibility of rollout and zero downtime from projects. It's like the biggest advantage of the human ordinate.

It is an open-source solution, so it is free to use. People on the internet always advocate for cheaper options. If you want to use a managed solution, you'll have to pay for it, and it can be expensive if you manage it on your own.

I rate this solution an eight out of ten. Regarding advice, if you have a small infrastructure, do not go with full Kubernetes. Instead, use smaller solutions like K3s or Rancher and full Kubernetes if you have a vast infrastructure.

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 are using the solution to deploy applications that are based on the microservices architecture.

The solution has many valuable features but the most impressive is the ability to scale an application and continuously monitor if all the components of the application are functioning correctly. If one part fails, it will recreate that component only, without disrupting the application. Another valuable feature, unlike other solutions that use the imperative way of programming this solution uses the declarative way, so you only need to describe the end result and it will do everything to arrive at that state.

The solution can be improved by adding a management console that will allow the use of a graphical interface to do what is usually done using command line instructions. I would like to have a simplification of the update process, which is currently not straightforward and time-consuming. The security of the solution is in its infancy and needs a lot of work.

I have been using the solution for over a year.

The solution is stable as long as you don't touch the configuration and you know what you are doing otherwise, it will crash easily.

The solution is scalable, but it is difficult to do as a standalone solution. Most organizations use paid solutions, such as Rancher, or OpenShift that are similar to operating systems that embedded the solution in them.

The initial setup is straightforward. I am able to have a fully working cluster within half an hour. There are tools available that can help automate the deployment and reduce the time to under 15 minutes.

The implementation was completed in-house.

The solution is open source and has no fees.

I give the solution eight out of ten.

I suggest anyone who would like to use this solution first get the certification. You must be knowledgeable with Linux and comfortable with the command line interface.

We have many applications that are running on top of Kubernetes.

The most valuable feature of Kubernetes is container orchestration.

Kubernetes can improve pod escalation.

In a future release, the dashboards could be more detailed. They are too simple.

I have been using Kubernetes for approximately five years.

Kubernetes is stable.

We have approximately 100 people using Kubernetes.

I have used the support from Kubernetes and it was good.

There is a license to use Kubernetes.

My company chose Kubernetes because it is the best tool for orchestration containers.

My advice to others that want to use this solution they should first study container concepts and create a POC.

I rate Kubernetes a nine out of ten.

Kubernetes is used to Dockerize and containerized applications.

Kubernetes has helped our organization by making our time-to-market better and the continuous integration and development are good. We can develop DevOps and FinOps methods.

The most valuable feature of Kubernetes is the integration with other solutions, such as Formative and Grafana.

Kubernetes could improve security. The security is really hard to deploy with proxies and other elements. Additionally, We have had some issues downloading repos and libraries.

In the next release, Kubernetes should develop a good interface for the administration and make the deployment of the solution easier.

I have been using Kubernetes for approximately six months.

Kubernetes is highly stable.

The scalability of Kubernetes is very good.

We have approximately 1,500 people using the solution in my organization. We have IT managers, administrators, and developers use it.

The support we have received has been very helpful.

I rate the support from Kubernetes a five out of five.

We have used other solutions previously, such as One Automation, and Nokia for traffic management.

The deployment of Kubernetes could be better. The initial setup took approximately a week to complete.

I rate the initial setup of Kubernetes a four out of five.

For our implementation strategy, we enabled a cluster in the production environment, dev environment, and pre-production environment and we made two masters and many nodes. However, it depends on the application and the traffic volume.

We use integrators for some of our deployments and for others we use only our team.

We use four of five administrators for the maintenance of the solution.

We have seen an ROI because the time it takes to market has been very quick to make a deployment.

Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services.

If you need to take care of proxies and configuration you may find the use of the GitHub repo Cube install helpful. It can help deploy and administrator the Kubernetes platform.

I rate Kubernetes an eight out of ten.

The following is a list of the cases when I prefer Kubernetes for application hosting:

1. Micro-services infrastructure + possible use of some service meshes, like Istio or Linkerd.
2. Cost efficiency; we are using Kubernetes in conjunction with AWS Spot Instances or Google Cloud preemptible VMs.
3. Standards-compliant infrastructures like HIPAA, PCI SOC, DSS, and ISOxxxx.
4. Highly-available or fault-tolerant infrastructures, due to some sort of self-recovery and self-healing.
5. Infrastructures with automatically scalable applications.

It's unified our technology stack across on-premises infrastructures and public clouds, including Amazon Web Services, Azure, and Google Cloud Platform. Kubernetes provides great integrations with other open-source tools, like Prometheus, Grafana, Elastic Stack, Fluentd, OAuth providers, and others.

Kubernetes distributions are also great because we adopt the platforms for different requirements. These include the AWS Elastic Kubernetes Service, Google Kubernetes Engine, Azure Kubernetes Engine, Rancher, etc.

It allows us to build custom-tailored infrastructures from small to big companies and satisfy various requirements, such as providing a proper level of RPO, RTO, scalability, cost-efficiency, and support high availability/fault tolerance.

The most valuable features of Kubernetes are:

1. Containers self-healing and self-recovery.
   
2. Unifications allow for internal Kubernetes components to be migrated between Kubernetes providers in an easier manner.
   
3. Kubernetes as a service from the major cloud providers including AWS, Google Cloud, Azure, Digital Ocean, IBM, etc. Kubernetes as a service helps in infrastructure migration from on-premises to cloud, or from cloud to cloud.
   
4. This product has a rich toolset from the community including CNI plug-ins, Helm packages, operators, dashboards, various integrations, etc.
   
5. Built-in scaling features, it's really great!

Some improvements that we would like to see are:

1. Have reacher built-in features and probably incorporate some features from the community toolset, like KEDA for pod scaling.
   
2. There are even more tools from the community for monitoring, log collectors, authorization, and authentication.
   
3. Have some sort of simplifications for wider adoption.
   
4. This product should have a more advanced built-in scheduler that uses real application metrics in the scheduling strategy.
   
5. Wider integration with cloud providers in terms of volumes and key management services.
   
6. Add support of traffic encryption option from container to container, and Ingress to the container.

We have been using Kubernetes as a self-hosted service, managed by external solutions, like Rancher, or a cloud-provider managed service (Azure AKS, Google GKE, Amazon EKS) for between three and four years.

This product is pretty stable, especially in the managed service option, but as with all platforms, it has some issues. As an example, during an update Kubernetes version on Amazon EKS from 1.17 to 1.18 Amazon duplicates workers count from 4 to 12 (should be from 4 to 8), upgrades takes more than 1 hour (should be about 10-20 minutes) and suddenly this leads to the short-time interruption of some applications during re-scheduling. In the end, we were forced to write our own rolling update scripts for updating the Kubernetes version on the nodes instances, which completes the upgrade in 10 minutes without application downtime. But again, this is an issue related to managed Kubernetes (in particular, Amazon EKS platform).

Great scalability, especially for the small and mid-size setup with fewer than 100 nodes.

We have used various platforms for managing Docker containers, such as Rancher, Azure App Service, and Portainer.

The first adoption was hard because the Kubernete's learning curve is pretty high.

The in-house team only.

It's open-source and free, so pricing should not be applied here.

Google Kubernetes Engine is free in the simplest setup, AWS Kubernetes Engine costs about $50 (depending on the region), in a three master setup, so it's almost the same as the cost of the EC2 instances and it's totally fine from my point of view.

We prefer Kubernetes due to the unification and the next level of the platform itself.