TrustRadius
Kubernetes is "the" tool for Docker orchestrationWe as an organization have very diverse hardware infrastructure. We have our own data centers and multiple cloud providers. The technologies we use are also again very diverse, we use VMs, containers as well as server-less technologies. When it comes to container technologies we are using Docker and orchestrate it with Kubernetes. In most of the cases, each Business unit have their own Kubernetes clusters for application hosting, and categorize it separately for preproduction and production environments.,Kubernetes can run anywhere, i.e in in-house datacenters as well as in Public cloud Very efficient management of containers and self healing. Out of the box Automated deployment and rollbacks. And support for many deployment strategies like blue-green, rolling update and recreate. Efficient secret and configuration management,Understanding Kubernetes is little hard and has a steep learning curve. Kubernetes is complex, it has its own concepts called pods, services and deployments. Debugging and troubleshooting in Kubernetes is quite hard and requires experience.,9,Kubernetes is one of the leading orchestrator for containers and also production ready. Helps use Docker containers confidently in production. Eliminates maintenance of Docker container lifecycle and handles it automatically. RBAC and Namespaces help is clear isolation and access management to applications and access members of team members to each application in a fine grained manner which boosts the confidence to use docker containers.,Swarm,Docker, Jenkins, Amazon Web ServicesKubernetes - the App Deployment Platform of the Future Today!Kubernetes has become the microservice container orchestration platform of choice. All our software deployed into Kubernetes - including public websites.,Scales extremely well Handles proper rolling updates of microservices Makes it super easy to establish a proper CI/CD pipeline Makes it easy for developers to adopt and therefore use,Could improve user access. Currently uses RBAC - but depending on your implementation (i.e. Amazon EKS) - setting up permissions and adding users to the cluster that are to use the cluster only is sometimes challenging. Security can always be improved Hooks for identity management; there are open source projects (i.e. Dex) - would be nice to see these adopted to the mainline UI Dashboard needs some major improvments,10,Has negated the need to hire people to manage deployment/operations as the development team can now work in a true ‘devops’ manner Biggest downtime is less than 5 minutes to upgrade a microservice; usually not even noticed by users Improved development cycle due to being able to implement a proper CI/CD pipeline,OpenShiftWorth the Learning CurveKubernetes has massively simplified and sped up the management of microservices deployed within my team. If we need to spin up a new service, even if it doesn't relate to the other services in the cluster, we can simply deploy the docker container to the cluster, complete with service discovery, configuration management, autoscale and fault tolerance. This is invaluable.,Fault tolerance - the things it does under the hood to handle failure is near magical. Configuration management - the ease of managing configs and secrets in kubernetes makes it a snap for integrating services. Service discovery - getting services to talk to each other with automated internal DNS and service-discovery makes shipping service dependencies easy.,Speed of error detection - many times, in attempting to fix a problem, I found that kubernetes just had a delay in handling an automated fix. By changing the system, I was playing a cat and mouse game with kubernetes' attempts to auto-fix the error. Sensible logging - many of the logs are difficult to decipher and too verbose to be useful. The learning curve is high - it took many months of working with Google, in which both I and Google Support Engineers learned a lot about how Kubernetes works. The learning curve is not for people looking for quick and easy out of the box.,10,The cost of running the services in kubernetes is orders of magnitude lower than our previous infrastructure. The speed of new service creation and deployment is amazing. The automatic failure recovery has saved us numerous times.,AWS ECS,New Relic Insights, Google Compute Engine, Google Cloud StorageKubernetes, a perfect home-grown container infrastructure management solutionKubernetes was used in my organization by a specific department. The business problem it attempted to address was resource allocation and scheduling. Creating and tearing down containers at will dependant on resource demand. These resources provided API services to the front-end website.,Resource allocation and scheduling. Managing container instances and run-files. Allowing for infrastructure as code.,Usability and user friendliness. There is no front end and anything attempting to provide a self-service model must be created currently. It uses pretty new technologies so there is a relatively steep learning curve.,7,The only negative impact would be time lost in research and development. It is possible that a lack luster understanding combined with a migration to kubernetes before being ready could lead to disastrous scenarios.,Mesos, Docker and Amazon Elastic Compute Cloud (EC2),Mesos, Mesosphere, DockerEasiest containerized deploy, bar none!It is being used across many departments, with more being added every day. My team was one of the first teams to use Kubernetes 8 for our microservice deployments. It addresses the problem of HDHA applications, agile development, rolling deployments with no downtime. We are also utilizing its service discovery with spring boot admin to provide node level details for all nodes in the cluster.,Single process microservice containerization that can be scaled up and down at a moments notice. Rolling deployments with zero downtime. Artifactory/DockerHub integration for deploying from an artifact repo. Spring Boot integration with configmaps & secret managment.,Ingress is HTTP only, so something that is TCP only must be in the cluster. Multi-process containers don't behave well. Sizing constraints cause slow startups for Spring Boot apps. Ingress' are slow to start up.,9,We switched from Chef, so we got a HUGE amount of ROI by switching our microservices over to Kubernetes 8. A lot less code, a lot easier to test, and immutable images means we have just one build and that artifact goes through all the environments. Automated deploys are SUPER easy with Kubernetes 8. We just have simple scripts listening on a GitHub repo for changes that applies/creates all the Kubernetes 8 pieces we need. Everyone has the power to deploy to any of the clusters through code and code reviews. Shrunk our devops need dramatically, everything just works.,Rackspace OpenStack and Chef,Docker, PostgreSQL, Jenkins
Unspecified
Kubernetes
34 Ratings
Score 9.1 out of 101
TRScore

Kubernetes Reviews

Kubernetes
34 Ratings
Score 9.1 out of 101
Show Filters 
Hide Filters 
Filter 34 vetted Kubernetes reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-7 of 7)
  Vendors can't alter or remove reviews. Here's why.
No photo available
July 09, 2018

Review: "Kubernetes is "the" tool for Docker orchestration"

Score 9 out of 10
Vetted Review
Verified User
Review Source
We as an organization have very diverse hardware infrastructure. We have our own data centers and multiple cloud providers. The technologies we use are also again very diverse, we use VMs, containers as well as server-less technologies. When it comes to container technologies we are using Docker and orchestrate it with Kubernetes. In most of the cases, each Business unit have their own Kubernetes clusters for application hosting, and categorize it separately for preproduction and production environments.
  • Kubernetes can run anywhere, i.e in in-house datacenters as well as in Public cloud
  • Very efficient management of containers and self healing.
  • Out of the box Automated deployment and rollbacks. And support for many deployment strategies like blue-green, rolling update and recreate.
  • Efficient secret and configuration management
  • Understanding Kubernetes is little hard and has a steep learning curve.
  • Kubernetes is complex, it has its own concepts called pods, services and deployments.
  • Debugging and troubleshooting in Kubernetes is quite hard and requires experience.
Kubernetes is a container-centric platform which can be run on in house data centers as well as public cloud. It is not only a platform run Docker containers, but also a very efficient network and application orchestrator. It has very powerful robust and extensible APIs. It is mostly declarative.
Read this authenticated review
No photo available
August 15, 2018

Review: "Kubernetes - the App Deployment Platform of the Future Today!"

Score 10 out of 10
Vetted Review
Verified User
Review Source
Kubernetes has become the microservice container orchestration platform of choice. All our software deployed into Kubernetes - including public websites.
  • Scales extremely well
  • Handles proper rolling updates of microservices
  • Makes it super easy to establish a proper CI/CD pipeline
  • Makes it easy for developers to adopt and therefore use
  • Could improve user access. Currently uses RBAC - but depending on your implementation (i.e. Amazon EKS) - setting up permissions and adding users to the cluster that are to use the cluster only is sometimes challenging.
  • Security can always be improved
  • Hooks for identity management; there are open source projects (i.e. Dex) - would be nice to see these adopted to the mainline
  • UI Dashboard needs some major improvments
Kubernetes is well suited for deployment of container based applications and microservices. Anything that doesn’t require a lot of disk space (i.e. a database) works really well with this system.
Read this authenticated review
Adam Eivy profile photo
October 05, 2017

Kubernetes Review: "Worth the Learning Curve"

Score 10 out of 10
Vetted Review
Verified User
Review Source
Kubernetes has massively simplified and sped up the management of microservices deployed within my team. If we need to spin up a new service, even if it doesn't relate to the other services in the cluster, we can simply deploy the docker container to the cluster, complete with service discovery, configuration management, autoscale and fault tolerance. This is invaluable.
  • Fault tolerance - the things it does under the hood to handle failure is near magical.
  • Configuration management - the ease of managing configs and secrets in kubernetes makes it a snap for integrating services.
  • Service discovery - getting services to talk to each other with automated internal DNS and service-discovery makes shipping service dependencies easy.
  • Speed of error detection - many times, in attempting to fix a problem, I found that kubernetes just had a delay in handling an automated fix. By changing the system, I was playing a cat and mouse game with kubernetes' attempts to auto-fix the error.
  • Sensible logging - many of the logs are difficult to decipher and too verbose to be useful.
  • The learning curve is high - it took many months of working with Google, in which both I and Google Support Engineers learned a lot about how Kubernetes works. The learning curve is not for people looking for quick and easy out of the box.
If you are managing microservices, need service-discovery, autoscale and config management, kubernetes provides everything you need right out of the gate with simple YAML config files, allowing you to store your infrastructure as code within your repos. Kubernetes works best with non-homogenous loads, so putting multiple types of services into the cluster that utilize different components (memory, CPU, network) will provide better results than a single service that takes up one type of resource.
Read Adam Eivy's full review
No photo available
July 31, 2017

Review: "Kubernetes, a perfect home-grown container infrastructure management solution"

Score 7 out of 10
Vetted Review
Verified User
Review Source
Kubernetes was used in my organization by a specific department. The business problem it attempted to address was resource allocation and scheduling. Creating and tearing down containers at will dependant on resource demand. These resources provided API services to the front-end website.
  • Resource allocation and scheduling.
  • Managing container instances and run-files.
  • Allowing for infrastructure as code.
  • Usability and user friendliness.
  • There is no front end and anything attempting to provide a self-service model must be created currently.
  • It uses pretty new technologies so there is a relatively steep learning curve.
Any sort of stateless service that is under heavy utilization or demand is a great candidate for containers in general and therefore kubernetes. Kubernetes should not be implemented in a specific department or for specific purposes. It is a general solution to a large problem and should be put to use accordingly.
Read this authenticated review
Jake Luby profile photo
March 28, 2017

Kubernetes Review: "Easiest containerized deploy, bar none!"

Score 9 out of 10
Vetted Review
Verified User
Review Source
It is being used across many departments, with more being added every day. My team was one of the first teams to use Kubernetes 8 for our microservice deployments. It addresses the problem of HDHA applications, agile development, rolling deployments with no downtime. We are also utilizing its service discovery with spring boot admin to provide node level details for all nodes in the cluster.
  • Single process microservice containerization that can be scaled up and down at a moments notice.
  • Rolling deployments with zero downtime.
  • Artifactory/DockerHub integration for deploying from an artifact repo.
  • Spring Boot integration with configmaps & secret managment.
  • Ingress is HTTP only, so something that is TCP only must be in the cluster.
  • Multi-process containers don't behave well.
  • Sizing constraints cause slow startups for Spring Boot apps.
  • Ingress' are slow to start up.
It is well suited for stateless microservices (single APIs that perform a single function, message consumers/producers, single session UIs, etc.). It is also great for teams that are deploying a lot since they are fast and rolling with no pods being down. It is not well suited for things that require a state or any kind of persistence layer in the app or cluster.
Read Jake Luby's full review
Manish Rajkarnikar profile photo
April 14, 2017

Kubernetes: "Poor man's review"

Score 10 out of 10
Vetted Review
Verified User
Review Source
  • Whole organization.
  • Used as a PaaS.
  • Used to deploy mostly stateless and cloud-ready apps.
  • Solves the problem of immutable infrastructure. No need for Chef, Puppet or Ansible.
  • Low learning curve for users.
  • Apps start on failure, can auto scale; burst into cloud;
  • Infra is cloud agnostic; works in an in-house datacenter too. Gives leverage to mangement for negotiations with cloud providers
  • Container orchestration
  • Application scale up and down
  • Good PaaS with fluentd, service discovery, secrets etc.
  • Huge community support
  • Free kubeconfig video, which is awesome
  • Quick releases (every quarter)
  • Extensive documentation. Design discussion and decisions are all documented.
  • Huge ecosystem and a lot of tools built around it. A lot of companies are behind it (Google, Microsoft, Coreos etc.). This project is not going anywhere.
  • Better documentation; no document versioning. Stuff is all over. It's difficult to find the right stuff sometimes.
  • Easy installation. kubeadm is partly there but not fully HA; minikube is awesome but does not work for multi-node installation; other installation such as kops, kargo are Anisible based, not fully immutable.
[Kubernetes is] suited for running docker containers in scale. I would not use it for running stuff like Cassandra, Hadoop, or a stateful application. Although they have stateful sets/pvc/pv. It's not there yet.
Read Manish Rajkarnikar's full review
David Long, SPA profile photo
February 06, 2017

Kubernetes Review: "The best way to run your containers"

Score 10 out of 10
Vetted Review
Verified User
Review Source
For managing containers across a cluster of servers, I won't use anything but Kubernetes. It makes scheduling containers extremely easy. Bundling applications that we develop into Docker images has made deployment a really simple process for us. It's made it so that we don't have to think too much about the clash that comes of running multiple applications on the same set of hosts. It's also helped our engineers to write idempotent applications better because we scale up and down often.
  • Container Scheduling
  • Deployments
  • Extensibility
  • SSL Management
  • Cluster Installation
  • Ingress Management
Kubernetes handles web applications wrapped into containers really well. Essentially, if it's something that you can containerize, Kubernetes will run it well. You can allocate resources towards specific containers if you have some that need more resources than others. Putting a service in front of containers makes it easy to communicate between pods of containers or the outside world.
Read David Long, SPA's full review

Kubernetes Scorecard Summary

About Kubernetes

Kubernetes is an open-source container cluster manager.
Categories:  Container Management

Kubernetes Technical Details

Operating Systems: Unspecified
Mobile Application:No