CoreOS rkt / Container Linux (project ended) vs Kubernetes

• Running a secure container without messing up with low-level details
• Very clear and straightforward approach to building a container
• A way to go for new projects thinking of containers
• Comprehensive and well-written documentation compatible with UNIX keep it simple way of thinking

Read full review

• Cost-effectiveness, Kubernetes is free and open source.
• Scalability, Kubernetes works regardless of how many pods it's managing; be it ten or a thousand.
• Low overhead, Kubernetes adds very little performance cost per developer per machine. The benefits of having a managed system vastly outweigh the minor performance cost.
• Large market share, Kubernetes is one of the top container orchestration tools used by developers today. This has been immensely helpful when finding new talent who are familiar with Kubernetes.

Read full review

• Market share, it's often very difficult to find new talent who use CoreOS rkt.
• Lack of wow features, CoreOS rkt doesn't necessarily offer any immediate advantages over other container solutions.

Read full review

• 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.

Read full review

• Developers spend less time configuring and more time coding.
• Less time training developers as CoreOS rkt lets them use whatever hardware and operating system they want.
• Reduced our IT costs, solutions are containerized using CoreOS rkt meaning they can write one solution with many developers in mind.

Read full review

• 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.

Read full review