Skip to content
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

Support Resource Pool #107

Open
sp-yduck opened this issue Oct 25, 2023 · 0 comments · May be fixed by #119
Open

Support Resource Pool #107

sp-yduck opened this issue Oct 25, 2023 · 0 comments · May be fixed by #119

Comments

@sp-yduck
Copy link
Collaborator

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

  • add new field in ProxmoxMachine.spec to specify resource pool name
    • cappx machine controller will add newly created vm to that resource pool
    • (?) cappx machine controller will create new resource pool if there is no resource pool yet
  • (?) add new field in ProxmoxCluster.spce to specify 'default' resource pool name
    • (?) cappx cluster controller will reconcile resource pool specified in the field
    • (?) cappx cluster controller will add cluster storage to the 'default' resource pool
    • (?) cappx machine controller will add newly created vm to 'default' resource pool if field is empty

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-proxmox version:
  • Proxmox VE version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@sp-yduck sp-yduck linked a pull request Nov 3, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant