Welcome to the Proxmox forum, maximcpp!
It depends on what you mean with restricting access to one or two nodes. In general, there's no general solution for this currently, since VMs are viewed as independent objects (except if they're limited in hardware capabilities, e.g. because of non-resource mapped PCI passthroughs), which can be migrated between nodes. What is you exact use case?
It depends on what you mean with restricting access to one or two nodes. In general, there's no general solution for this currently, since VMs are viewed as independent objects (except if they're limited in hardware capabilities, e.g. because of non-resource mapped PCI passthroughs), which can be migrated between nodes. What is you exact use case?
thank you for answer, Daniel!
I’m trying to allocate one or two nodes on a production cluster for dynamically creating vms via API (using terraform or similar tools). These VMs will be created and destroyed as needed. I want to isolate the access for developers working on this solution from the rest of the productive landscape in that datacenter, Daniel
oh, vm names are dynamic
vm ids also dynamic
I’m trying to allocate one or two nodes on a production cluster for dynamically creating vms via API (using terraform or similar tools). These VMs will be created and destroyed as needed. I want to isolate the access for developers working on this solution from the rest of the productive landscape in that datacenter, Daniel
oh, vm names are dynamic
vm ids also dynamic
Last edited: