Kubernetes is an open-source container cluster manager.
N/A
Proxmox VE
Score 8.9 out of 10
N/A
Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC. Users can manage virtual machines, containers, highly available clusters, storage and networks via a web interface or CLI. Proxmox VE code is licensed under the GNU Affero General Public License, version 3. The project is developed and maintained by Proxmox Server Solutions GmbH.
$90
year & CPU socket
Pricing
Kubernetes
Proxmox VE
Editions & Modules
No answers on this topic
Community
€ 90
year & CPU socket
Basic
€ 280
year & CPU socket
Standard
€ 420
year & CPU socket
Premium
€ 840
year & CPU socket
Offerings
Pricing Offerings
Kubernetes
Proxmox VE
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Proxmox Virtual Environment's source code is published under the free software license GNU AGPL, v3 and thus is freely available for download, use and share. A Proxmox VE Subscription is an additional service program that helps IT professionals and businesses keep Proxmox VE deployments up-to-date. A subscription provides access to the stable Proxmox VE Enterprise Repository delivering software updates and security enhancements, technical help and support.
More Pricing Information
Community Pulse
Kubernetes
Proxmox VE
TrustRadius Insights
Kubernetes
Proxmox VE
Highlights
Research Team Insight
Published
Users have found Proxmox VE ideal for its flexibility and robustness in varied environments, leveraging its capabilities for virtualization and deployment in both lab settings and real-world applications. It has been particularly beneficial for businesses that need a solution that supports clustering, works with existing hardware, and offers features like high availability, snapshot backup, and live migration, thus solving their complex multi-technology integration issues. Proxmox VE users appreciate its capacity to support a mixture of storage options and virtual machines across different departments, focusing on its ability to simplify management and increase operational efficiency.
In comparison, Kubernetes serves predominantly as a container orchestration platform used extensively for managing microservices, with broad adoption across organizational departments. Users celebrate Kubernetes for its effectiveness in automating deployment, scaling, and management of containerized applications. The platform is favored for scenarios requiring quick deployment of services, reliability, and scalability, such as dynamic microservice environments in cloud setups. Kubernetes finds particular merit in use cases that demand robust service discovery, auto-scaling, and resource-efficient handling of cloud-native applications, illustrating its capacity to streamline cloud infrastructure management.
Both Kubernetes and Proxmox VE are championed for their flexibility and the efficiencies they bring to technology infrastructure management. While Proxmox VE is noted for its virtualization functionality and versatility in supporting complex technology ecosystems, Kubernetes is lauded for its container management and the ability to foster rapid and scalable application development and operation. This distinction highlights Proxmox VE as suitable for environments requiring traditional virtualization with broad storage solutions, whereas Kubernetes is ideal for modern, container-driven applications that benefit from a rapid development lifecycle and cloud-based deployment.
Features
Kubernetes
Proxmox VE
Container Management
Comparison of Container Management features of Product A and Product B
Kubernetes
8.4
Ratings
8% above category average
Proxmox VE
-
Ratings
Security and Isolation
8.50 Ratings
00 Ratings
Container Orchestration
9.50 Ratings
00 Ratings
Cluster Management
9.50 Ratings
00 Ratings
Storage Management
7.00 Ratings
00 Ratings
Resource Allocation and Optimization
7.50 Ratings
00 Ratings
Discovery Tools
8.50 Ratings
00 Ratings
Update Rollouts and Rollbacks
8.50 Ratings
00 Ratings
Self-Healing and Recovery
8.50 Ratings
00 Ratings
Analytics, Monitoring, and Logging
8.00 Ratings
00 Ratings
Server Virtualization
Comparison of Server Virtualization features of Product A and Product B
Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.
Proxmox VE is a virtualization platform that provides a range of features and functionalities suitable for various scenarios. Here are some specific scenarios where Proxmox VE is well suited and some scenarios where it might not be the best choice:Well-suited scenarios:Virtualization of server workloads: Proxmox VE is well suited for virtualizing server workloads such as web servers, mail servers, database servers, and other similar applications. Its high-performance virtualization capabilities allow these workloads to run smoothly and efficiently.Hosting multiple virtual machines (VMs): Proxmox VE is ideal for hosting multiple VMs on a single server. It provides efficient resource management, allowing users to easily allocate resources to each VM.Clustered environments: Proxmox VE is a great choice for clustered environments. It supports clustering and can easily manage multiple servers, providing high availability and load balancing for mission-critical applications. Less appropriate scenarios: Limited hardware resources: Proxmox VE requires significant hardware resources to run efficiently. If you have limited hardware resources, it might not be the best choice. Simple applications: If you only need to run a single, simple application, Proxmox VE might be overkill. Other virtualization platforms or even a basic web hosting service might be more appropriate.
ZFS storage out of the box. The integration with ZFS is fantastic. You can easily create pools to store your VM images and data on, and the Proxmox web UI provides an easy way to check drive health, ZFS scrub status, etc.
Great web UI. Practically everything configurable is available to do so from the web user interface. You'll rarely need to drop to the command line for administrative tasks, unless you want to, in which case you can do that too. The UI also provides graphs and visualisations to help you keep check of how everything is performing.
Easy to setup a high availability cluster. Although Proxmox VE works perfectly well on a single server, you can also install it on multiple hosts and setup a cluster.
Uses a Debian core system with an Ubuntu based kernel. This means everything to do with the base operating system is tried and trusted. We use a lot of Debian and Ubuntu installs, so having this run underneath Proxmox VE was an added bonus for us.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The web UI does not work as well on mobile devices. It is useable, but a mobile optimised / responsive UI would be nice to have. There is a mobile app, so that may alleviate this issue, but I have not yet tried it.
Support in the community forums could be better. There are paid support plans, but new users trying out the software will not have access to this. Answers to questions can sometimes be terse, and I can imagine this may put some people off.
The wiki is a bit hit and miss with certain topics. I've often seen outdated or missing information, and the whole thing looks like it could do with some polish. I'd love to see it opened up for the community to add to.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
Proxmox VE provides the most capable, yet stable virtualization platform in the market today. Licensing options are also competitive and cost-effective for support, and support is extremely fast and knowledgable of getting issues resolved as quickly and soundly as possible.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
The interface is easy to use for most of it, but still lacks screens for some configurations. Also, a few of the screens are not as intuitive as they could be. This is specially true with disk and network configuration, where some graphic/visual representations of the configurations would be very useful
Proxmox VE's ha-cluster functionality is very much improved, though does have a not-very-often occurrence of failure. In a 2-node cluster of Proxmox VE, HA can fail causing an instance that is supposed to migrate between the two nodes stop and fail until manually recovered through the command-line tools provided. Other than this, the HA clustering capability of Proxmox VE has proven to be reliable in 3 or more clustered environments with much less chance of these failures to occur.
Proxmox VE's interfacing is always fast to load, both the Web interface and the command-line tool interfaces. Reporting is practically real time almost all the time, and you can see everything in mere seconds, easily able to identify if something is wrong or it everything is in tip-top shape as always desired
As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.
Proxmox VE provides everything you need to quickly add new storage mediums, network and local, as well as networking interfaces, such as using Linux standard bridges and now Open-vSwitch bridges which can be even more scalable than before. Proxmox VE 4.0 dropped support for OpenVZ in favor of the more well supported and native LXC and made an upgrade path to it very simple.
