Proxmox VE
Virtual machineproxmox
Open source virtualization platform combining KVM virtual machines and LXC containers with optional clustering and HA.
- Provider
- default
- Kind
- Virtual machine
- Category
- Compute
- Also known as
- PVE
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| clustered | boolean | — | no | false | inherited |
| diskEncryption | boolean | — | no | — | inherited |
| highAvailability | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| memoryGib | integer | — | no | — | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | inherited |
| publicIp | boolean | — | no | — | inherited |
| sizeVcpu | integer | — | no | — | inherited |
| storageBackend | enum | lvm-thin | zfs | ceph | nfs | directory | no | lvm-thin | inherited |
| virtualizationType | enum | kvm | lxc | no | kvm | inherited |
| zoneRedundant | boolean | — | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "proxmox", component: "proxmox" }Auto Scalingalibaba-auto-scalingElastic Compute Servicealibaba-ecsEdge Node Servicealibaba-ensSimple Application Serveralibaba-simple-application-serverAmazon EC2aws-ec2Amazon EC2 Auto Scalingaws-ec2-auto-scalingAmazon EC2 Dedicated Hostsaws-ec2-dedicated-hostAmazon Elastic VMware Serviceaws-evsAmazon Lightsailaws-lightsailAWS Nitro Enclavesaws-nitro-enclaveAzure BareMetal Infrastructureazure-baremetal-infrastructureAzure Compute Fleetazure-compute-fleetAzure Dedicated Hostazure-dedicated-hostAzure Data Science Virtual Machineazure-dsvmNutanix Cloud Clusters on Azureazure-nutanix-cloud-clustersAzure Virtual Machinesazure-virtual-machineAzure Virtual Machine Scale Setsazure-vm-scale-setAzure VMware Solutionazure-vmware-solutionCrusoe Cloud VMcrusoeFirecrackerfirecrackerMicrosoft Hyper-Vhyper-vKubeVirtkubevirtLambda Cloud instancelambda-labsKVM with libvirtlibvirtNebius AI Cloud VMnebiusNutanix AHVnutanix-ahvOpenStack Novaopenstack-novaoVirtovirtRunpod PodrunpodVast.ai instancevast-aiGeneric virtual machinevirtual-machineVMware vSpherevsphereXCP-ngxcp-ngXenServerxenserverDigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpuDropletsdigitalocean-dropletDroplet Autoscale Pooldigitalocean-droplet-autoscaleBare Metal Solutiongoogle-bare-metal-solutionCloud TPUgoogle-cloud-tpuCompute Enginegoogle-compute-engine
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # Proxmox VE, an open source virtualization platform. Per the "Proxmox VE Administration Guide" it combines # KVM full virtualization with LXC containers, runs on a single node unless a cluster is assembled, and # treats high availability as an opt-in feature of a multi-node cluster. schemaVersion: "1" type: "component" id: "proxmox" kind: "virtual-machine" provider: "default" docs: "https://pve.proxmox.com/pve-docs/pve-admin-guide.html" aliases: ["PVE"] defaults: managed: false properties: virtualizationType: type: "enum" values: ["kvm", "lxc"] default: "kvm" clustered: type: "boolean" default: false highAvailability: type: "boolean" default: false storageBackend: type: "enum" values: ["lvm-thin", "zfs", "ceph", "nfs", "directory"] default: "lvm-thin"