-
Notifications
You must be signed in to change notification settings - Fork 44
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
Generic Cluster API provider instead of specific instances #162
Comments
@ncdc yes, that crossed my mind. After implementing the CAPA and CAPV it looks like a generic CAPI maybe what is needed. |
Where you potentially could add some provider-specific logic would be for accessing the remote host, as some clouds have APIs that let you do this securely instead of using SSH. But even then, you could probably do that by injecting a connector, such as |
@srm09 ^^^ |
@ykakarap I'm wondering if you've put together any ideas for this? Thanks! |
Hi @ncdc , @vladimirvivien and I had a few discussions around this. We are looking at what needs to be done to achieve this and do not have it completely formalized. |
Is the plan to continue down this route? Was hoping to get a |
@srm09 the plan is to investigate/create a generic capi-provider that can enumerate its machines. But if investigation reveals that is not doable, then we could stay on the current course. |
Would it be possible to combine
capa_provider
andcapv_provider
to a more genericcluster_api_provider
? Having specific providers for specific Cluster API infrastructure providers means you have to add new providers to the language for Azure, GCP, etc.The text was updated successfully, but these errors were encountered: