No more typing reviews! Try our Samantha, our new voice AI agent.

Cisco Container Platform [EOL] vs Kubernetes comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Cisco Container Platform [EOL]
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Kubernetes
Average Rating
8.6
Reviews Sentiment
7.4
Number of Reviews
80
Ranking in other categories
Container Management (3rd)
 

Featured Reviews

CM
Cloud Architect, Feltus Lab at Clemson University
Enables the deployment/management of Kubernetes clusters from multiple resource providers at one location
One thing I have not really had the chance to explore too much is the Cisco Container Platform command-line interface. I've been told that exists and it's functional, but I'm not sure if it's really made for end-users. It might just be for admins or developers. One thing that is a little bit annoying about Cisco Container Platform is that for each cluster you create you have to go through the same web form each time. If you're creating two identical clusters, you still have to go through that web form twice. What's really nice about most platforms is that they have command-line interfaces where you can just copy a single command which has all the flags with all the configurations you want and put that in a text file. Then, when you want to create another cluster you can just paste that in and edit one or two flags if you want to. You don't have to go through a web form every time and that is a feature that I would like to see in the future with CCP. It would be nice, at the end, once you create a cluster using the web form, if it would give you a single command that you could copy and put somewhere and then paste it, in the future, to create an identical cluster or an almost identical cluster. I would like the ability to save cluster configurations to CCP. I've provided that feedback to the development team. There might even be a version that is out which already has that functionality integrated into it. I think it's safe to say that at some point in the future that feature will be provided.
RV
DevOps Engineer at a tech services company with 11-50 employees
Automated deployments and self-healing have transformed how I run reliable chat services
For improvements, I would definitely suggest some enhancements to Kubernetes. While Kubernetes is very powerful, there are still a few areas where it could be improved. Our challenge is the learning curve and operational complexity. For new team members, concepts such as networking, RBAC, Ingress, and troubleshooting distributed systems can take time to understand. Better built-in onboarding tools or simplified abstractions would help. Another pain point is debugging and observability. While kubectl provides good basic visibility, deep debugging across multiple services, pods, and nodes often requires external tooling such as Prometheus, Grafana, or centralized logging. Stronger native observability features would be very helpful. Networking and Ingress configuration can also be complex, especially when dealing with certificates, routing rules, and cloud-specific integrations. A more standardized experience across environments could reduce operational overhead. From a cost perspective, managing and optimizing resource usage at scale still requires careful monitoring and tuning. Better built-in cost visibility would be very helpful. For the needed improvements, I think that covers most of my main concerns. The biggest areas for improvement are still around simplifying operations, better native observability, and easier cost visibility. If I had to add one more point, it would be around standardization and developer experience. Sometimes different clusters, cloud providers, or tooling setups behave slightly differently, which increases maintenance efforts. More consistent defaults and opinionated best practices could help teams adopt Kubernetes faster and with fewer surprises. Overall, despite these challenges, Kubernetes is a very mature and reliable platform, and the benefits clearly outweigh the limitations for most production use cases. An additional area that could be improved is upgrade and version management. While managed services help coordinate Kubernetes version upgrades, API deprecations and compatibility with add-ons can still be time-consuming and risky for production environments. Better tooling and clearer migration automation would make upgrades safer and easier. Another improvement could be around documentation, consistency, and discoverability. Kubernetes documentation is very comprehensive, but for beginners, it can sometimes be overwhelming to navigate and identify best practice paths.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is definitely the fact that you can use a single platform to deploy to different resource providers. Right now, the version I'm using has vSphere and AWS, but I know in the future they're planning on adding more. The ability to deploy clusters on-prem or to any number of public cloud providers is really valuable because you don't need to relearn or switch platforms to switch resource providers."
"The best feature is autoscaling. It's effortless to use for scaling deployment parts, CI/CD, etc."
"The solution is easy to use."
"The best thing about Kubernetes is that most of the containerized applications are centralized."
"I rate Kubernetes nine out of ten."
"There is no licensing fee; the solution involves the use of an open source tool."
"I would highly recommend this solution to anyone who is considering using it."
"The high availability of containerization is most valuable, as we get density with planning containers, and the self-serving feature allows our developers to grab a container and complete testing, always in the cloud or locally integrated with Ceph or cluster."
"The Kubernetes cluster is easy to maintain on the container orchestration, very stable with outward scalability and good performance, which is very important for our platform."
 

Cons

"One thing that is a little bit annoying about Cisco Container Platform is that for each cluster you create you have to go through the same web form each time. If you're creating two identical clusters, you still have to go through that web form twice."
"The solution can be quite complex for many users."
"It is not a quick-to-learn product if you are not from a Linux background."
"The virtual machines should be GUI-based"
"The solution is still complex to manage. It requires specialists to the extent that I wouldn't be able to ask a junior employee to manage the software."
"They should update Kubernetes more regularly."
"Currently, in Kubernetes, all of the health deployments or monitoring, and the discrete tools need to be configured. Changing this would make it much easier. Otherwise, we have to rely on a external tool to implement the monitoring."
"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."
"Kubernetes is a complex solution. The product needs to be more manageable and user-friendly."
 

Pricing and Cost Advice

Information not available
"I am using the solution's open-source version."
"It's an affordable solution"
"This is an open-source solution, so there are no licensing costs associated with its use."
"There are no licensing fees."
"In addition to Kubernetes, you have to pay for support."
"There is no licensing fee."
"If you have a solid AKS and a solid DevOps process, you'll automatically get an ROI, not just in terms of cost but also in how quickly you can see your business application progress."
"The solution is affordable."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
902,417 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Construction Company
11%
Manufacturing Company
9%
Computer Software Company
9%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business26
Midsize Enterprise10
Large Enterprise49
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Kubernetes?
My experience with pricing and setup costs shows that Kubernetes itself is open source and free, so there is no licensing cost for the software. The main cost comes from the infrastructure and mana...
What needs improvement with Kubernetes?
For improvements, I would definitely suggest some enhancements to Kubernetes. While Kubernetes is very powerful, there are still a few areas where it could be improved. Our challenge is the learnin...
What is your primary use case for Kubernetes?
My main use case for Kubernetes is deploying and managing scalable backend services and web applications in a production-like environment. For example, in one of my projects, a real-time chat appli...
 

Also Known As

Cisco CCP
K8
 

Overview

 

Sample Customers

Clemson University
China unicom, NetEase Cloud, Nav, AppDirect
Find out what your peers are saying about Red Hat, Amazon Web Services (AWS), Kubernetes and others in Container Management. Updated: June 2026.
902,417 professionals have used our research since 2012.