Kubernetes Reviews

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.

I am using Kubernetes for particular projects.

The most valuable feature of Kubernetes is automation. It is the best tool for automation.

I have been using Kubernetes for approximately two years.

The stability of Kubernetes is very good. It does not go down.

All of our DevOps engineers are using Kubernetes in my company.

The initial setup of Kubernetes is difficult. However, if you are used to the flow then it is easier. The length of time it takes for the implementation depends on the project.

My company chose Kubernetes because it has automatic deployment.

If it is your first time using Kubernetes then you will have to study how to use it and learn how to do scripts.

I rate Kubernetes a seven out of ten.

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.

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.

Kubernetes is a container management platform, and all our microservices are deployed on this platform.

There are features that come out of the box with Kubernetes, with respect to scaling, reliability, etc. It's the leading container management platform. There are other competing ones, but this is the leading one.

It has multiple instances of the application running. If one of them goes down, the other one automatically spins up.

It would be nice if they could make it easier for developers and infrastructure staff to automate some of the pieces that they have to do manually at the moment.

This is a solution I've been using for four or five years.

It's stable. It's managed by the cloud provider.

Depending on the SLAs with respect to scalability, we can scale up and down as per our demand. We could increase the number of nodes instantaneously for our requirements. In our company, we have 5,000 people around the world using Kubernetes.

As for initial setup, If it is on an on-premises environment then it's a little bit tricky, but if it's on public cloud, then they have an offering where you can spin up clusters within minutes. Those are managed by the cloud providers. On cloud platforms, the initial setup is easy, but if you want to spin up your own cluster and manage that, then it could be a lot of work. Spinning up might be easy, but maintaining that cluster could be a lot of work.

Look at your use cases to make sure that Kubernetes is required. It is generally required when there are concerns with scalability or when there is a need for a solution that is highly available and highly scalable. If this is the case, then it makes sense to use Kubernetes.

It could be used as a global tool as well. Some of the nodes would be on-premises and on the cloud or multi-cloud.

However, if you have a simple application which is used by your own company and some internal applications, and is not used by many people, and scalability is not the concern, then you shouldn't go for Kubernetes.

I would rate this solution at eight on a scale from one to 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.

If our project requires a cloud deployment we will use a cloud provider's version of Kubernetes. For example, Azure or AWS Kubernetes Elastic Services. We try to make use of whatever is provided by the cloud providers. 

If the project requires an on-premise solution we use products from various vendors, such as Red Hat or other open-source products that can be downloaded and installed for free.

We are using Kubernetes for container management.

Kubernetes use cases are typically containerized application hosting. This is the basic use case that we do. Another use case can be deploying new application microservices which are loosely coupled and containerized using microservices-based architectures.

We can achieve a reduction of almost 50% to 60% of effort in operations by using Kubernetes.

The most valuable feature is the Zero Touch Operations, which involves a new way of performing operations and support. We do not have to do maintenance, the operations are very simple.

Kubernetes can improve by providing a service offering catalog that can be readily populated in Kubernetes. 

The service catalog, for example, could be a CRM application on Kubernetes or an eCommerce retail application packaged on Kubernetes and to be readily deployable. Instead of somebody trying to figure out all the configurations of hosting this on Kubernetes, if something was readily available, which the developers for these CRM or eCommerce products, they could partner with either AWS, Google, or Azure and make the deployment of such applications readily available on Kubernetes. 

This would allow very little work for a business to go live. The business can quickly straight away and subscribe, launch, and use. It is not difficult for an IT team to be involved to create an application environment to start up. It's would be much easier for businesses to use it directly and start off the applications.

I have been using Kubernetes for approximately three weeks.

The stability of Kubernetes depends on how we have designed it. Our design is stable because I know how to design it and if something goes wrong how to fix it.

The scalability is superb, it is highly scalable.

We have 75,000 employees in our organization that is using this solution.

Technical support is not used very frequently. We use advanced-level support occasionally. It is only in certain circumstances when we have some advanced complexity that we reach out to an expert.

A person with a moderate level of knowledge on Kubernetes, with the help of the community forum, and documentation, most of their problems can be solved.

We do not need any particular company, such as Red Hat, to come in and support the Kubernetes environment, or some other company, such as Ubuntu Canonical to be signed up for a contract to support Kubernetes. It's not required.

The initial setup is straightforward, it was not complex.

The maintenance for Kubernetes is very minimal.

You need to pay for a license if you buy branded products. For example, if you take the services from Azure, AWS, or Google, the price of the Kubernetes cluster is inclusive of the service that's being offered to us on a pay-and-use model.

I haven't tried all the advanced features of Kubernetes, but I feel it is meeting most of the requirements of a new design architecture for applications to be hosted. I don't see any particular functionality which is not available for me as of now.

The open-source ecosystem is providing lots of ideas to solve all kinds of problems. The open-source ecosystem of developers, implementers, and integrators is providing lots of ideas. If there is something I may not know, I look up to the community forum and receive answers. There are no issues of finding something, however, Kubernetes by itself has to improve. It is a matter of the implementer to discover ideas to solve the problem. The Kubernetes engine is designed very well.

I would highly recommend this solution to others.

I rate Kubernetes a nine out of ten.

Kubernetes is a container-based platform that is used for microservices-based applications. 

You can containerize and deploy your ports, as well as expose them over the internet, to get your applications running.

The performance is good.

The services it provides you are good.

It runs in multiple availability zones.

The configuration is a bit complicated.

Because the platform provided is so simple, additional configuration is required to get your apps up and running.

There are some issues with the upgrades. When updates are released, the older versions are decommissioned. 

The updates are quite frequent and are lengthy. It takes about an hour each time.

I have been working with Kubernetes for approximately two years.

It's cloud-agnostic Kubernetes, we have it available in Azure, AWS, and GCP.

In the two years that I have been using Kubernetes, I have not experienced any issues with the stability of this solution.

Our main e-commerce application is running in Kubernetes. Currently, we have three applications running, and we are trying to onboard different applications.

You need to have knowledge of Kubernetes to manage the cluster and to complete the deployment.

It can take 20 to 30 minutes to configure the Kubernetes cluster.

Once the setup is complete you can have your dependencies running in Kubernetes.

You need a core technical person, who is a DevOps engineer who has experience working on Kubernetes to deploy and maintain this solution.

We evaluated ECS, which is a service offered by Amazon.

It's an orchestration tool, but it has certain limitations.

I would highly recommend this solution to anyone who is considering using it.

I would rate Kubernetes a nine out of ten.