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

• Makes sure that the workload remains UP & running by maintaining the desired state.
• Gives a lot of flexibility in choosing the networking, storage, monitoring, etc solutions of your choice.
• The biggest advantage is to upgrade the application with a new version without any downtime.
• Portability of the code is possible up to a great extent.

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

• We had several problems with its NFS, which is responsible for syncing the code across the cluster
• On several instances the pods go into UNKNOWN state in which case restarting the entire node is the only solution
• As a user of the existing setup given to me, I wasn't able to allocate only some CPU cores on a single host. It was either all or zero making cluster utilization sub-optimal

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

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Read full review