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

feat: external managed cluster registration and node handling #73

Open
chrxmvtik opened this issue Dec 2, 2024 · 2 comments
Open

feat: external managed cluster registration and node handling #73

chrxmvtik opened this issue Dec 2, 2024 · 2 comments

Comments

@chrxmvtik
Copy link

Hello fellas,

Since cloudstack kubernetes provider is successor of cloudstack cloud controller, shouldn't it also allow to register external managed clusters automatically? I am not saying it should be mandatory, but would be great if we had a choice. So it would fetch information about nodes and register cluster to the cloudstack, besides that it could handle node removal if virtual machine is removed and so on.

@Pearl1594
Copy link
Contributor

Pearl1594 commented Dec 2, 2024

Currently, CAPC clusters - K8S clusters deployed using cluster API on CloudStack, can be viewed on CloudStack UI; with the UI providing a centralized view to all of the ACS resources used by this external cluster.
In the upcoming release of CloudStack, we have added support to import external nodes - VMs or baremetal/physical servers as worker nodes to managed CKS clusters. Just wanted to highlight what currently exists and maybe coming in the next release, in case they meet your requirements in some way.

@chrxmvtik
Copy link
Author

Currently, CAPC clusters - K8S clusters deployed using cluster API on CloudStack, can be viewed on CloudStack UI; with the UI providing a centralized view to all of the ACS resources used by this external cluster. In the upcoming release of CloudStack, we have added support to import external nodes - VMs or baremetal/physical servers as worker nodes to managed CKS clusters.

Yes, that is one way to achieve that, however we don't always have possibility to deploy using CAPI and we have to stick to what we have. Hence why I opened 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

No branches or pull requests

2 participants