-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM is created at each reconciling #29
Comments
Hi @themoriarti, Could you please let me know the version/release of the operator and Proxmox you're using? The latest versions of Kubemox do not have a constant reconciliation mechanism. The project originally included continuous reconciliation loops, but I removed that functionality. I want to implement a custom external resource watcher for Proxmox (see #25). Additionally, it's correct that the operator doesn't depend on the VMID. Kubemox relies on the virtual machine name, which is not a unique value per VirtualMachine or LXC in Proxmox. |
Hi @alperencelik. |
Hi @themoriarti, I'm unable to reproduce the issue. I reviewed the code and couldn't understand what might be triggering another reconciliation mechanism. Is there a chance that the As you can see once the VirtualMachine creation got completed the operator verifies the VirtualMachine exists and running.
|
Create a virtual machine from template by cloning. New virtual machine with the same name and a different id is created once a minute with each reconcile. After starting VM manualy, the creation of new ones stops.
This can be caused by different names and an incorrectly created virtual machine.
But it is very desirable that the newly created VM be registered by ID because it is unique, but the name is not unique.
Example:
The text was updated successfully, but these errors were encountered: